Skip to main content
Glama
Sign In
Math-MCP

Math-MCP

by EthanHenrickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

median

Calculate the median of a list of numbers for accurate statistical analysis. Input an array of numerical values to derive the central value in the dataset.

Instructions

Calculates the median of a list of 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": {
      "numbers": "<numbers>"
    },
    "name": "median"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYesArray of numbers to find the median of

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It does not mention how the median is computed (e.g., sorting, averaging middle values for even-length lists), edge cases, or return format. This is insufficient for a math utility.

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 with no wasted words. It is appropriately front-loaded and earns its place.

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 low complexity and lack of output schema, the description is minimally adequate. However, it omits behavioral details like sorting and handling of even-length arrays, which an agent would need to fully understand the tool's operation.

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?

Schema description coverage is 100%, so baseline is 3. The description does not add new meaning beyond what the schema provides; it merely echoes the function. No extra context like valid ranges or formatting is given.

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 that the tool calculates the median of a list of numbers, using a specific verb and resource. It implicitly distinguishes from siblings like mean and mode, but does not explicitly contrast them, preventing a perfect 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 median over alternatives (e.g., mean, mode) or any context-specific advice. No when-not or alternative tool mentions are included, limiting decision support.

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

Related Tools