CCDV-F practice questions: Tools and MCPs.

A tool parameter may only be one of three values. How do you express that?

• Describe the three allowed values in the tool description text and validate the string in your handler
• Set tool_choice to the tool's name so the model cannot pass other values
• Split the capability into three separate tools, one per allowed value
• Use an enum in the parameter's JSON schema and list the parameter under required

What does a tool_result with is_error set to true tell the model?

• The API will retry the tool automatically on the next turn
• The tool has been removed from the tools list for the session
• The conversation must end and the client should surface the error text to the user
• The call failed and the content explains why, so the model can adapt

What is tool_choice set to 'any' for?

• Require the model to call some tool this turn, without naming which
• Let the model decide whether to call a tool or answer in text
• Force the model to call one specific named tool
• Allow the model to call several tools in parallel within one assistant turn

Your app connects to an MCP server over streamable HTTP. What must the client handle?

• Session handling and authentication for the remote server
• Selecting which model the server should use for its tools
• Spawning the server as a local subprocess over stdio
• Compiling the server from source before each connection

Which is a good tool description?

• 'Retrieves order information. Call this whenever the user asks anything about orders, shipping, refunds, or accounts.'
• 'Look up an order by order_id. Use when the user cites an order number. Returns status, items, shipping; errors on unknown id.'
• 'Order lookup tool. Accepts an id string and returns the order record from the orders service as JSON.'
• 'Fetch order details. See the internal API docs for parameter names, return fields, and error codes.'

How should a tool report that a required parameter was missing?

• Raise an exception so the agent loop terminates cleanly
• Return an empty success result so the model moves on
• Return an error result naming the missing parameter
• Fill in a sensible default and note it in the result