Skip to main content
Glama

Sample spread by group

bpj_table_group_dispersion
Read-onlyIdempotent

Estimate within-group sample standard deviations, returning null for singleton groups.

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": {
      "rows": "<rows>",
      "group": "<group>",
      "column": "<column>"
    },
    "name": "bpj_table_group_dispersion"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already establish this as a safe read-only, idempotent, closed-world operation. Beyond that, the description adds two genuinely useful traits: it computes the sample (not population) standard deviation, and it returns null for singleton groups, which tells the agent how degenerate groups are handled. The output shape and error behaviour on malformed 'rows' remain undisclosed, keeping it from a 5.

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?

It is one front-loaded sentence with no filler; the verb and resource come first and the edge-case rule follows. It is efficient, though the extreme brevity leaves the described gaps elsewhere rather than being a structural flaw in itself.

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 three-required-parameter tool that accepts a serialized record array, the definition is thinner than the complexity warrants: the format expectations for 'rows' and the returned structure (presumably group value mapped to standard deviation) are unstated. The null-for-singleton note covers the most important edge case, but an agent still cannot predict the response shape.

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%, so all three required parameters depend on their bare titles ('Record array (JSON)', 'Grouping column', 'Column name') for meaning. The description never mentions rows, group, or column, nor that 'group' and 'column' are field names resolved against the JSON in 'rows'. That relationship is the single most important thing to convey and it is absent.

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 names a specific statistic and scope: 'Estimate within-group sample standard deviations'. That distinguishes it from siblings such as bpj_table_group_mean or bpj_table_group_median by the statistic computed. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus an alternative, and no stated prerequisites, such as whether 'rows' must be a JSON array string. The singleton-group note describes behaviour, not usage. The agent must infer that 'group' and 'column' name fields inside the supplied rows.

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.