Definition
An MCP tool is a named capability that an AI client can call through an MCP server.
A tool is not just a button for the model. It has a name, a description, an input schema, and an execution path. The client uses the catalog to decide whether a tool is relevant, then sends structured arguments when it calls the tool.
Good tools are specific. A tool called search_orders with clear filters is usually safer and easier for a model to use than one broad tool that accepts arbitrary instructions.
What makes a good MCP tool
The best tools are narrow, well-described, and easy to validate.
- The name should describe the action or resource.
- The description should say when to use the tool and what it returns.
- The input schema should be structured and constrained.
- The execution path should validate inputs before touching the source system.
- The result should be useful without leaking secrets or unnecessary internal details.
OpenAPI operation tools
OpenAPI operations can map naturally to MCP tools.
An operation like GET /orders/{id} can become a tool with schema-aware arguments and an editable description. The MCP server can then route the call to the upstream REST API or another executor.
The description matters because AI clients use it to choose the right tool. Agent-ready descriptions reduce guesswork and make tool use more predictable.
Database tools
Database MCP tools should separate metadata from execution.
Schema tools should describe approved tables, columns, keys, relationships, and permissions without returning row payloads. Executor tools should run only after trusted server-side validation.
Common questions
Is an MCP tool the same as an API endpoint?
Not exactly. An MCP tool can wrap an API endpoint, database executor, local function, or other capability. The tool is the AI-facing interface.
Why do tool descriptions matter?
AI clients use descriptions to decide which tool to call. A vague description can cause wrong tool selection or poor arguments.
Should one tool do many jobs?
Usually no. Narrow tools with clear schemas are easier to validate, observe, and explain.