Skip to main content
Glama

Numeric summary and quartiles

bpj_numeric_summary
Read-onlyIdempotent

Calculate mean, median, quartiles, extrema and population standard deviation.

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": {
      "values": "<values>"
    },
    "name": "bpj_numeric_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: the deviation is explicitly the *population* variant, which is a methodological choice an agent cannot infer from the schema. It says nothing about handling of empty input, non-numeric entries, or output shape.

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

Conciseness4/5

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

A single well-formed sentence with no filler, and the core purpose is front-loaded. It is perhaps too terse for a tool whose only parameter is unformatted, but nothing in it is wasted.

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?

With no output schema, the description carries the burden of describing the return value; listing the statistics partially does that job, but the format of the result and the treatment of edge cases are unspecified. The input encoding gap also remains unaddressed, leaving the definition only minimally sufficient for correct invocation.

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?

Schema description coverage is 0% for the single required parameter `values`, which is typed only as a string with an 8000-character cap. The description never explains that this is a number series, nor the expected delimiter or encoding (comma-separated, whitespace, newline, JSON array), which is the main thing an agent could get wrong. This is the definition's most consequential gap.

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?

Specific verb ("Calculate") plus a precise enumeration of the computed statistics (mean, median, quartiles, extrema, population standard deviation), so an agent knows exactly what the tool produces. It does not name or distinguish itself from any sibling, but the enumerated statistic set is distinctive enough on its own.

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?

There is no statement of when to use this tool, when not to, or what alternative to prefer for a related task (e.g. a different summary or a single-statistic tool). The agent must infer applicability purely from the statistics listed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.