Skip to main content
Glama

zscore_calculate

Read-onlyIdempotent

Calculate z-score, cumulative probability, and percentile from an observed value, mean, and standard deviation to measure how far a data point deviates from the average.

Instructions

Calculate z-score, cumulative probability, and percentile for a value given mean and standard deviation.

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": {
      "value": "<value>",
      "mean": "<mean>",
      "stddev": "<stddev>"
    },
    "name": "zscore_calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
meanYesPopulation mean.
valueYesThe observed value.
stddevYesPopulation standard deviation (positive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description usefully enumerates the three returned quantities (helpful given no output schema) but omits the key behavioral assumption — that cumulative probability and percentile presume a normal distribution — which materially affects interpretation of results.

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?

A single front-loaded sentence that names the operation, the outputs, and the inputs with zero filler. Nothing is buried or redundant.

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 small pure-math tool with full schema coverage and safety annotations, the description is nearly sufficient, and it compensates for the absent output schema by naming the return values. The missing normality assumption and any note on what a percentile return means are the only notable gaps.

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 all three parameters (value, mean, stddev) are already documented including that stddev must be positive. The description's 'given mean and standard deviation' merely restates the schema and adds no format, range, or edge-case detail beyond baseline.

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?

Specific verb (Calculate) plus the exact set of outputs (z-score, cumulative probability, percentile) and the required inputs, so the operation is unambiguous. It does not, however, distinguish itself from overlapping siblings such as normal_distribution or percentile_calc.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives, despite siblings like normal_distribution, percentile_calc, and descriptive_stats occupying adjacent territory. The agent must infer that this tool takes summary statistics rather than a data array.

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

Deploy Server

Other Tools