Skip to main content
Glama
Drakoxw

MCP Server Demo

by Drakoxw

sum

Add two integers together to calculate their total. This tool performs basic arithmetic addition for numerical values.

Instructions

Suma dos números.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:13-16 (registration)
    The sum tool is registered using the @mcp.tool() decorator, which exposes the function as an MCP tool.
    @mcp.tool()
    def sum(a: int, b: int) -> int:
        """Suma dos números."""
        return a + b
  • server.py:14-16 (handler)
    The sum handler function that takes two integer parameters (a, b) and returns their sum. The function signature also serves as the schema definition.
    def sum(a: int, b: int) -> int:
        """Suma dos números."""
        return a + b
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic function ('Suma dos números') without any information on error handling, performance, side effects, or output format. This is insufficient for a tool with parameters and an output schema.

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 with a single sentence ('Suma dos números'), which is front-loaded and wastes no words. It efficiently communicates the core function without unnecessary elaboration.

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 simplicity (two integer parameters) and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema description coverage, it lacks details on parameter semantics and behavioral context, making it incomplete for optimal agent use.

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

Parameters2/5

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

The schema description coverage is 0%, and the description does not add any meaning beyond the input schema. It doesn't explain what 'a' and 'b' represent, their constraints, or examples of usage, leaving the parameters undocumented in both the schema and description.

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 'Suma dos números' clearly states the tool's purpose with a specific verb ('Suma') and resource ('dos números'), making it immediately understandable. It doesn't distinguish from its sibling tool 'get_exchange_rate', which is unrelated, but the purpose is unambiguous.

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. It doesn't mention any prerequisites, constraints, or comparison with other tools, leaving the agent to infer usage solely from the tool name and description.

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/Drakoxw/mcp-server'

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