Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Statistics of numbers: mean, median, standard deviation, percentiles

math_stats
Read-only

Descriptive statistics for a list of numbers: count, sum, mean, median, mode, min, max, range, population and sample variance and standard deviation, quartiles with IQR, and the 90th, 95th and 99th percentiles (linear interpolation). Up to 10,000 numbers, comma or space separated. Use to summarise measurements, latencies, prices or scores without a spreadsheet. Example: values=12, 15, 15, 18, 21, 24, 30, 45. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
valuesYesNumbers separated by commas, spaces or new lines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, but the description goes further by disclosing the 10,000-number cap, the interpolation method for percentiles, and a full billing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free). Crucially, "each call is charged, so repeats are not free" explains the otherwise puzzling idempotentHint=false — exactly the kind of context annotations cannot carry.

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?

Front-loaded with purpose and output inventory, then limits, use case, example, and cost — a sensible ordering with no filler sentences. The percentile/output enumeration is long but each item is independently informative rather than redundant.

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

Completeness5/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 fully compensates by listing every returned statistic and the interpolation convention. Input format, size cap, and cost are all covered, so an agent has everything needed to call it correctly and knows the cost consequence of repeating a call.

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?

There is only one parameter and the schema already documents it at 100% coverage ('Numbers separated by commas, spaces or new lines'). The description adds the 10,000-element limit and a concrete example, which are useful constraints beyond the schema, but the per-parameter meaning is largely already supplied.

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?

States a specific verb and resource ('descriptive statistics for a list of numbers') and enumerates the exact outputs: mean, median, mode, variance, standard deviation, quartiles/IQR and 90/95/99th percentiles with linear interpolation. This clearly separates it from siblings like math_evaluate (expression evaluation) and text_stats (text analysis).

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

Usage Guidelines4/5

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

"Use to summarise measurements, latencies, prices or scores without a spreadsheet" gives a concrete when-to-use context, and the worked example anchors the expected input shape. It does not explicitly name an alternative or state when not to use it, so it stops short of the top score.

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.