Skip to main content
Glama

stats

Read-only

Computes descriptive statistics, correlations and linear fits from numbers, text, or CSV columns, covering mean, median, mode, SD, quartiles, outliers, percentiles, skew, histograms, Pearson/Spearman.

Instructions

Statistics: mean, median, mode, sd, quartiles, outliers, percentiles, skew, histogram; with y/y_column Pearson, Spearman, linear fit. Input numbers, free text or CSV (column by name or 1-based).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
yNo
pathNoor a file
textNo
columnNo
numbersNo
y_columnNo
delimiterNo
histogramNo
percentilesNo0-100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. Because there is no output schema, the enumerated statistic list (mean, median, mode, sd, quartiles, outliers, skew, histogram, Pearson/Spearman/linear fit) usefully discloses what comes back, but the description says nothing about sd conventions (sample vs population), outlier definition, minimum sample size, or result ordering.

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?

Compact and front-loaded with the tool's identity, then the output set, then input modes. The telegraphic phrasing ('with y/y_column Pearson, Spearman, linear fit') is terse enough to be slightly cryptic but wastes no words.

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?

For a 9-parameter tool with no output schema and low schema coverage, the description covers most input semantics but omits delimiter behavior, precedence among the three input modes, and any note on how results are structured when a histogram or percentiles are requested. Adequate but with clear gaps.

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?

With only 22% schema coverage across 9 parameters, the description does real work: it maps numbers, text, path (CSV file), and column (by name or 1-based) to their meanings and ties y/y_column to Pearson/Spearman/linear fit. It leaves delimiter unexplained and does not say whether numbers vs path takes precedence when both 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?

Names the specific resource (descriptive statistics plus correlation/regression) and enumerates the exact measures produced, so an agent knows this is the numeric-stats tool. It does not explicitly distinguish itself from siblings like text_stats, calc, or matrix, so it stops short of a 5.

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 through the input-mode sentence ('Input numbers, free text or CSV'), which tells the agent how to feed data but not when to choose this over text_stats or calc. There are no exclusions or explicit alternative routing.

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