Skip to main content
Glama
NitinUdasin

MCPServerDemo

by NitinUdasin

add

Add two integer numbers together using this arithmetic tool from MCPServerDemo. Perform basic addition calculations with specified values.

Instructions

add two numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:13-18 (handler)
    The 'add' tool is defined here using the @method decorator. It performs simple integer addition and returns a JSON-RPC Success result.
    @method
    def add(a: int, b: int) -> Result:
        logger.info(f"Received add request with params: a={a}, b={b}")
        result = a + b
        logger.info(f"Add operation result: {result}")
        return Success(result)
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'add two numbers' reveals nothing about error handling, rate limits, authentication needs, or output format. It lacks any behavioral context beyond the basic operation.

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 at three words, front-loaded with the core action. Every word earns its place by directly contributing to understanding the tool's purpose without any redundant or unnecessary 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?

Given the tool's low complexity (simple arithmetic), 2 parameters, and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks behavioral details and usage context, making it incomplete for fully informed tool selection.

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?

With 0% schema description coverage, the description must compensate for parameter documentation. 'add two numbers' implicitly defines the two parameters as numbers to be added, which aligns with the schema's integer types. However, it doesn't specify parameter names or detailed constraints, leaving some ambiguity.

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

Purpose4/5

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

The description 'add two numbers' clearly states the verb ('add') and resource ('two numbers'), making the tool's function immediately understandable. However, with no sibling tools, it cannot demonstrate differentiation from alternatives, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives or any contextual prerequisites. It simply states what the tool does without indicating appropriate scenarios or constraints for its application.

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/NitinUdasin/MCPServerDemo'

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