Skip to main content
Glama

Tukey outlier fences

bpj_series_tukey_fences
Read-onlyIdempotent

Locate observations outside the linear-quartile 1.5 IQR fences.

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_tukey_fences"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds the specific 1.5 IQR fence rule, but it does not disclose the return shape, handling of missing or non-numeric values, or whether fence boundaries are inclusive.

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?

The definition is a single sentence with no filler and places the key operation first. It is compact and front-loaded.

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 one-parameter statistical tool with no output schema, the description is under-specified. It does not say whether the result is a set of values, indices, a mask, or a count, nor does it clarify the input encoding.

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?

The single 'values' parameter has 0% schema description coverage, so the description needs to compensate. It does not explain the required JSON array string format, maximum length, null handling, or numeric constraints beyond what the schema title minimally implies.

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 operation: locating observations outside linear-quartile 1.5 IQR fences. This identifies a Tukey outlier-fence operation distinctly from generic quantile or summary siblings, though it does not explicitly name any alternative.

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 only implied by the operation itself: an agent can infer this is for outlier detection under Tukey's 1.5 IQR rule. There is no explicit when-to-use, when-not-to-use, or comparison to alternatives such as MAD-based outlier detection.

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.