Skip to content
BENIBIX Learn

MCP Tool

AI🔌 MCPServer Features

Also known as Tool (MCP), MCP Tools

An action an MCP server lets the model call, like a search.

Think of it like

Think of it like a button with a label on it. The helper reads the label, then presses it.

Example

Lucy's calendar server offers a tool called create_event. When she asks for a meeting on Friday, the model calls it with the date and time.

Why it matters

Tools are how a model acts in the world through MCP. They are the part that can do harm, so they need the most care.

Definition

An MCP tool is an action that a server lets the model call, such as sending an email or running a search. Each tool has a name, a description and a schema that lists its inputs. The client asks the server for its tools and hands them to the model. When the model calls one, the server runs it and returns the result. Tools are controlled by the model, so hosts often ask the user before a risky one runs.

Example code

json
{
  "name": "create_event",
  "description": "Add an event to the calendar.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "title": { "type": "string" },
      "start": { "type": "string" }
    },
    "required": ["title", "start"]
  }
}
A tool as the server lists it: a name, a note for the model, and the inputs it needs.
The client lists the tools, the model calls one, and the server runs it and replies.

Common mistake

Writing a thin description. The model picks tools from their descriptions, so a vague one gets the wrong call.

Key takeaways

  1. 1
    Model decides. When to call it.
  2. 2
    Name, note, inputs. All three matter.
  3. 3
    Server runs it. Then returns the result.

Compare