CCAR-F practice › Tool Design & MCP Integration · Question 36 of 105
Tool Design & MCP Integration
A document analysis subagent has a generic fetch_url tool. It sometimes loads search result pages and blog posts instead of the source papers it was given. What is the best fix?
Show answer and explanation
Answer: B — Replace fetch_url with a load_document tool that validates the URL points to a document
A constrained tool that only accepts valid document URLs makes the misuse impossible while still covering the agent's job (b). A description warning (a) reduces but doesn't prevent misuse. Post-filtering (c) still spends the call and the context on the wrong page. Coordinator approval (d) adds a round trip to every fetch to work around a tool that is too general.
Keep going
More Tool Design & MCP Integration questions
- An extraction pipeline must call extract_metadata before any enrichment tools, because…
- A classification step offers the model three tools and must always produce one of them…
- A team's .mcp.json, committed to the repository, configures a GitHub MCP server with an…
- A team is standardizing Claude Code MCP setup. They need Jira for everyone, and one…
- An agent is connected to an internal MCP server whose search_code tool indexes all 40…