API Hub MCP — 337+ Tools

descriptive_statistics

Calculate descriptive statistics including mean, median, mode, standard deviation, min, max, and quartiles from a list of numbers.

Instructions

Calculate descriptive statistics: mean, median, mode, std dev, min, max, quartiles.

Parameters:
    numbers — Comma-separated numbers (e.g. '1,2,3,4,5') or JSON array.

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

Input Schema

Name	Required	Description	Default
`numbers`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description should fully disclose behavior. However, it does not mention handling of invalid inputs, edge cases (e.g., empty arrays, non-numeric values), or the return format (though an output schema exists). It lacks transparency about potential errors or limitations.

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?

The description is concise with a clear purpose statement, a bullet-like list of statistics, and a parameter explanation. It is front-loaded but could be more structured with clear labeling of sections.

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?

For a tool with one parameter and an existing output schema, the description adequately covers what the tool does and how to provide input. It lists the computed statistics, though it omits details like output format for quartiles. Overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the tool description adds meaning to the 'numbers' parameter by specifying it accepts comma-separated numbers or a JSON array. This clarifies the input format beyond the schema's bare type 'string'.

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 uses a specific verb 'Calculate' and lists the resource 'descriptive statistics' including a clear enumeration of outputs (mean, median, mode, etc.). It distinguishes itself from siblings by being a general stats tool, not a specialized one like calculate_correlation.

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 this tool over alternatives, no exclusions or prerequisites. It simply states what it does without context for selection among many similar statistical tools.

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

Deploy Server