MCP & Tool Protocols
Tool schema
A machine-readable description of a tool's name, inputs, and expected structure.
Example
A tool schema specifies that `city` is required and must be text.
Why it matters
It helps an AI or application prepare requests a tool can understand.
You'll hear it
“The tool expects a date here, not a general description.”
Can you control it?
Set by the team
The people building or running the AI choose this setup. An everyday user generally needs their help to change how this part works.
Common questions
- Does a correct schema ensure a safe action?
- No. A valid request can still target the wrong record or exceed the user's intent.
- Can an unclear description cause the wrong values to be supplied?
- Yes. Both the structure and its explanation affect how requests are prepared.
- Can the schema change after an update?
- Yes. Connected applications may need adjustments when accepted fields or types change.