Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Run a t-test with confidence interval

statistics_t-test
Read-onlyIdempotent

One-sample, two-sample (Welch or pooled) and paired t-tests with the estimate, statistic, degrees of freedom, p-value, confidence interval and Cohen's d from caller-supplied numbers. Pure computation; no data is stored or fetched. Price $0.02 USDC. POST /api/v1/statistics/t-test. An unpaid call returns the x402 payment terms and does not run.

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": {
      "kind": "<kind>",
      "x": "<x>"
    },
    "name": "statistics_t-test"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesx, array. Required.
yNoy, array. Optional.
mu0Nomu0, number. Required.
kindYeskind, string, one of one_sample, two_sample, paired. Required.
confidenceNoconfidence, number. Required.
alternativeNoalternative, string, one of two-sided, less, greater. Required.two-sided
equalVarianceNoequalVariance, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
nNon. Object.
ciNoci. Array.
dfNodf. Number.
sdsNosds. Object.
kindNokind. String.
meansNomeans. Object.
pValueNopValue. Number.
cohensDNocohensD. Number.
sourcesNosources. Array.
estimateNoestimate. Number.
statisticNostatistic. Number.
droppedRowsNodroppedRows. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost ($0.02 USDC), transport (POST /api/v1/statistics/t-test), and critically the payment failure mode: an unpaid call returns x402 payment terms instead of a result. The annotations cover safety/idempotency, and the description adds the commercial and error-path context an agent needs before invoking.

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-loads the capability, then behavior, then pricing and endpoint, in four tight sentences with no filler. The opening sentence is slightly run-on and drops its verb, but nothing is 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?

An output schema exists, so return values need no explanation, and the description still names them for scanning. Payment flow, purity of computation, and input sourcing are all covered, leaving nothing an agent needs missing before a call.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning by mapping the two-sample variants to the equalVariance parameter (Welch vs pooled) and clarifying that x/y are caller-supplied numbers rather than references. It does not explain mu0, confidence, or alternative beyond the schema.

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 statistical operation with its three variants (one-sample, two-sample Welch/pooled, paired) and enumerates what it returns (estimate, statistic, df, p-value, CI, Cohen's d). An agent can distinguish this from statistics_anova or statistics_nonparametric-tests by the named test family alone.

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?

Provides clear context that inputs are caller-supplied and nothing is fetched or stored, which tells the agent it must compute from raw arrays rather than reference a dataset. It does not, however, say when a t-test is the right choice versus ANOVA or a nonparametric alternative, so selection against siblings is left to the caller.

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