Skip to main content
Glama

Standard error of the sample mean

bpj_series_mean_standard_error
Read-onlyIdempotent

Divide the sample standard deviation by the square root of the observation count.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds the formula, which explains what is computed, but says nothing about edge cases (zero or one observation), the JSON-string input form, or what is returned.

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?

A single efficient sentence with no filler. Its brevity is appropriate, though it leaves out the input and output framing that would make the definition actionable.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool this is thin: there is no output schema, no statement that a scalar standard error is returned, and no explanation of the required JSON-array string input. Only the arithmetic is specified.

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

Parameters2/5

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

Schema description coverage is 0% and there is one required parameter. The description only refers obliquely to 'observation count', not to the 'values' parameter, its JSON-encoded string format, or the 12000-character limit, so it does not compensate for the schema gap.

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?

The description states a specific computation (sample standard deviation divided by the square root of the count), which identifies standard error of the mean and distinguishes it from the sibling mean tools. It stops short of naming the operation as 'standard error' or referencing the input/output, so it is clear but not fully self-contained.

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 guidance, no mention of alternatives such as the mean tools, and no stated preconditions (e.g. minimum sample size). The agent must infer that this is the dispersion-of-the-mean tool rather than a mean calculator.

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.