Skip to main content
Glama

curatedapi

Statistics calculator

calc_math_statistics
Read-only

Mean, median, mode, range, variance and standard deviation (population and sample) of a list of numbers.

Computes descriptive statistics exactly. Sums, means and variances are exact fractions; standard deviations are square roots computed with certified arithmetic, so even long lists of decimals give correctly rounded results with no accumulated floating-point error.

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": "calc_math_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYesThe data, as a list of numbers. 1 to 10000 items.
optionsNoPrecision and rounding of the results (default: rounding=half_even, significant_digits=15).

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world, notably non-idempotent), so the description's job is to add computation behavior — and it does, disclosing exact-fraction arithmetic, certified square-root rounding, and freedom from accumulated floating-point error. It does not contradict the annotations, though it explains little about how the precision options interact with that exactness.

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?

Two sentences, zero waste. The list of computed statistics is front-loaded and the exactness claim follows as supporting justification rather than burying the lead.

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?

With an output schema present and full input-schema coverage, the description needs only to establish scope and precision behavior, which it does well. The one missing piece is interaction between the precision options and row/edge-case behavior (e.g. ties, single-element lists), which is a modest gap for a simple pure-computation tool.

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 both `values` and the nested `options` (decimals, rounding, significant_digits) are already documented with ranges and defaults elsewhere; a 3 is the baseline. The description adds only the general notion of rounding controls, not any new meaning, and never explains what happens when both decimals and significant_digits are supplied.

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 enumerates exactly which statistics are produced (mean, median, mode, range, variance, population and sample standard deviation) for a list of numbers, so the resource and operation are unambiguous. It does not explicitly differentiate itself from neighbors such as calc_math_rounding or calc_math_expression, but the enumerated outputs make the distinction inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the emphasis on exact fractions and correctly rounded square roots signals that this tool is for cases where floating-point drift matters, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer routing from the math alone.

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.

Resources