Skip to main content
Glama
kylekanouse

Demo MCP Server

by kylekanouse

Multiplication Tool

multiply

Calculate the product of two numbers by multiplying them together. Enter two numeric values to get their multiplication result.

Instructions

Multiply two numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYesFirst number
bYesSecond number

Implementation Reference

  • Handler function that multiplies two input numbers a and b, returning a text response with the result in the format 'a × b = result'.
    async ({ a, b }) => ({
      content: [
        {
          type: "text",
          text: `${a} × ${b} = ${a * b}`
        }
      ]
    })
  • Zod input schema defining two required number parameters: a and b.
    inputSchema: {
      a: z.number().describe("First number"),
      b: z.number().describe("Second number")
    }
  • Registration of the 'multiply' tool on the MCP server instance, specifying name, title, description, input schema, and inline handler function.
    server.registerTool(
      "multiply",
      {
        title: "Multiplication Tool",
        description: "Multiply two numbers",
        inputSchema: {
          a: z.number().describe("First number"),
          b: z.number().describe("Second number")
        }
      },
      async ({ a, b }) => ({
        content: [
          {
            type: "text",
            text: `${a} × ${b} = ${a * b}`
          }
        ]
      })
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Multiply two numbers' implies a mathematical operation but reveals nothing about error handling, numeric limits, precision, or return format. It doesn't address whether it handles integers, floats, or specific edge cases, leaving significant behavioral gaps.

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 perfectly concise at three words, front-loading the core action without any wasted text. Every word earns its place, making it immediately understandable while maintaining brevity.

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

Completeness2/5

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

For a mathematical operation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (product, error messages), numeric constraints, or behavioral characteristics. The simplicity of the operation doesn't compensate for these omissions in context.

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 parameter documentation, so the baseline is 3. The description 'Multiply two numbers' adds no additional parameter semantics beyond what the schema already provides (two numbers labeled 'a' and 'b'), maintaining the adequate baseline without enhancement.

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 'Multiply two numbers' clearly states the verb ('Multiply') and resource ('two numbers'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'divide' beyond the obvious mathematical operation difference, which is why 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 like 'add', 'subtract', or 'divide'. There's no mention of context, prerequisites, or comparative use cases, leaving the agent to infer usage purely from the tool name.

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/kylekanouse/Test-MCP---DEMO-MCP-Dev-1'

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