Skip to main content
Glama
fongfai

Minimum Viable MCP Project

by fongfai

sum_numbers

Add two numbers to calculate their sum. This tool takes two numeric inputs and returns the total as structured output.

Instructions

Add two numbers and return structured output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYesFirst number
bYesSecond number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
expressionYes

Implementation Reference

  • The sum_numbers tool handler implementation. Takes two numbers (a and b), calculates (a + b) * 100, and returns structured output with the result and expression string.
    server.registerTool(
      "sum_numbers",
      {
        description: "Add two numbers and return structured output.",
        inputSchema: {
          a: z.number().describe("First number"),
          b: z.number().describe("Second number"),
        },
        outputSchema: {
          result: z.number(),
          expression: z.string(),
        },
      },
      async ({ a, b }) => {
        const result = (a + b ) * 100;
        const structuredContent = {
          result,
          expression: `${a} + ${b} = ${result}`,
        };
    
        return {
          content: [
            {
              type: "text",
              text: structuredContent.expression,
            },
          ],
          structuredContent,
        };
      }
    );
  • Input and output schema definition for sum_numbers tool. Input requires two numbers (a, b). Output defines result as number and expression as string.
    server.registerTool(
      "sum_numbers",
      {
        description: "Add two numbers and return structured output.",
        inputSchema: {
          a: z.number().describe("First number"),
          b: z.number().describe("Second number"),
        },
        outputSchema: {
          result: z.number(),
          expression: z.string(),
        },
      },
  • src/server.ts:40-70 (registration)
    Registration of sum_numbers tool with the MCP server using server.registerTool, including name, description, schemas, and handler function.
    server.registerTool(
      "sum_numbers",
      {
        description: "Add two numbers and return structured output.",
        inputSchema: {
          a: z.number().describe("First number"),
          b: z.number().describe("Second number"),
        },
        outputSchema: {
          result: z.number(),
          expression: z.string(),
        },
      },
      async ({ a, b }) => {
        const result = (a + b ) * 100;
        const structuredContent = {
          result,
          expression: `${a} + ${b} = ${result}`,
        };
    
        return {
          content: [
            {
              type: "text",
              text: structuredContent.expression,
            },
          ],
          structuredContent,
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'return structured output,' which hints at the return format, but doesn't specify what that structure entails, error handling, or any constraints like numeric limits. This leaves significant gaps for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's function without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 simplicity (basic arithmetic), 2 parameters with full schema coverage, and the presence of an output schema, the description is reasonably complete. It covers the core purpose and hints at the output, though it could benefit from more behavioral details given the lack of annotations.

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

Parameters3/5

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

The input schema has 100% description coverage, with clear documentation for both parameters ('a' and 'b'). The description adds no additional meaning beyond the schema, as it doesn't explain parameter interactions or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the action ('Add two numbers') and the resource ('numbers'), making the purpose immediately understandable. However, it doesn't distinguish from the sibling 'ping' tool, which is unrelated, so it doesn't fully differentiate from alternatives.

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 in what context it should be applied. It simply states what it does without any usage context or exclusions.

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/fongfai/mcp'

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