Add two integers together to calculate their sum. This mathematical tool performs basic addition operations for numerical calculations.
Adds two numbers together.
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | ||
| b | Yes |
@mcp.tool()
def add(a: int, b: int) -> int:
"""Adds two numbers together."""
return a + bDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States the mathematical operation but omits details like return value format, overflow behavior, or whether the operation is atomic/reversible.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with zero waste. Front-loaded and appropriately sized for the tool's trivial complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for the low complexity (2 integer params, no nested objects), but lacks return value description and error handling details given the absence of output schema or annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% (titles 'A' and 'B' not sufficient). Description mentions 'two numbers' implying the parameter count and types generally, but does not map them to parameters 'a' and 'b' or explain their semantic roles (e.g., addends).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb ('adds') and resource ('two numbers'), but does not explicitly differentiate from sibling 'hello_world' tool (though the distinction is obvious).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no guidance on when to use this tool versus alternatives, nor any prerequisites or contextual conditions for invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chaitanyaatlan/fifth-elephant-mcp-workshop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server