Skip to main content
Glama
Sign In
mcp-demo

mcp-demo

by AmAzing129
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Calculator

calculate

Perform arithmetic operations on two numbers: add, subtract, multiply, or divide.

Instructions

Perform basic arithmetic on two numbers

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>",
      "a": "<a>",
      "b": "<b>"
    },
    "name": "calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst operand
bYesSecond operand
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It fails to mention error handling (e.g., division by zero), return format, or any side effects. Only states basic arithmetic, which is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 6 words, but it is under-specific. While concise, it lacks necessary detail for a 3-parameter tool, making it merely adequate.

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 simplicity of the tool and no output schema, the description covers the basic purpose but omits edge cases, return values, and usage details needed for complete understanding.

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?

With 67% schema coverage, the description adds no additional meaning beyond the schema's property descriptions. The operation enum values are listed in schema but no further elaboration in description.

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 'Perform basic arithmetic on two numbers', which specifies the verb (perform), resource (arithmetic on two numbers), and distinguishes from sibling tools like add_note and get_current_time.

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?

No explicit guidance on when to use this tool vs alternatives. While the sibling tools are obviously different, the description lacks any context about usage scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools