Skip to main content
Glama
parameshwaran1

Deployable MCP Server

add

Perform basic addition of two numbers. Input two numeric values, and the tool calculates their sum for quick computation tasks.

Instructions

Add two numbers together.

Args:
    a: First number
    b: Second number
    
Returns:
    The sum of a and b

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'add' tool handler, registered via @mcp.tool() decorator. It adds two integers i and j and returns their sum. Includes type hints and docstring serving as schema.
    @mcp.tool()
    def add(i:int , j:int) -> int:
        """
        Adds two integers and returns the result.
        
        Args:
            i (int): The first integer to add.
            j (int): The second integer to add.
        
        Returns:
            int: The sum of i and j.
        """
        return i+ j
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it states the basic operation and return value, it doesn't disclose behavioral traits like error handling (e.g., for non-numeric inputs), performance characteristics, or any constraints. The description is minimal but doesn't contradict annotations.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured sections for Args and Returns. Every sentence earns its place with no wasted words.

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

Completeness4/5

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

Given the tool's low complexity (simple arithmetic) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers purpose, parameters, and return semantics, though it lacks behavioral details like error cases.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It adds meaningful semantics by explaining that 'a' is the 'First number' and 'b' is the 'Second number', which clarifies their roles beyond the schema's generic titles. However, it doesn't specify format details like integer vs. float.

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 clearly states the specific action ('Add two numbers together') and identifies the resource (numbers). It distinguishes from sibling tools like 'divide', 'multiply', and 'subtract' by specifying the exact mathematical operation.

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

Usage Guidelines3/5

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

The description implies usage through its mathematical context but doesn't explicitly state when to use this tool versus alternatives like 'subtract' or 'multiply'. No explicit guidance on when-not-to-use or prerequisites is provided.

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

Related Tools

  • @GonTwVn/GonMCPtool
  • @riteshbangal/BuildMcpServer
  • @liaotaodcx8/toolkittest
  • @bahfahh/mcptest
  • @kelseyee/mcp_calculator
  • @joeguo911/mcp-demo

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/parameshwaran1/mcpserverexample'

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