Skip to main content
Glama

add

Calculate the sum of two numeric values. Provide two numbers to get their total.

Instructions

Sum two numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'add' tool handler: sums two float numbers. Registered via @mcp.tool() decorator at line 79.
    @mcp.tool()
    def add(a: float, b: float) -> float:
        """Sum two numbers."""
        return a + b
  • The @mcp.tool() decorator on line 79 registers the 'add' function as an MCP tool named 'add' on the FastMCP instance.
    @mcp.tool()
    def add(a: float, b: float) -> float:
        """Sum two numbers."""
        return a + b
  • Input schema: 'a' (float), 'b' (float). Return type: float. The function signature serves as the schema definition via FastMCP introspection.
    @mcp.tool()
    def add(a: float, b: float) -> float:
        """Sum two numbers."""
        return a + b
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses the basic behavior of adding two numbers, which is sufficient for such a simple operation. Since no annotations are provided, the description carries the full burden, and it is clear and transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single sentence. Every word is purposeful, and there is no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple arithmetic tool with an output schema, the description provides the essential information. However, it lacks guidance on edge cases, precision, or return value details, which could be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description 'Sum two numbers.' does not add any meaning to the parameters a and b beyond the input schema. With 0% schema description coverage, the description should compensate, but it fails to elaborate on what the parameters represent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Sum two numbers.' clearly states the action (sum) and the resource (two numbers). It distinguishes this tool from sibling arithmetic operations like divide, multiply, and subtract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or scenarios where addition is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiegKat/mcp-agent-blackboard'

If you have feedback or need assistance with the MCP directory API, please join our Discord server