Skip to main content
Glama

Threshold exceedance rate

bpj_series_exceedance
Read-onlyIdempotent

Count observations strictly above a threshold and return their share.

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>",
      "threshold": "<threshold>"
    },
    "name": "bpj_series_exceedance"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
thresholdYes

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 fully covered. The description adds the meaningful boundary rule 'strictly above' (excluding values equal to the threshold) and hints that the result is a proportion rather than a raw count. It does not say what the denominator is (only observations? all values including NaN?) or how a zero-length input behaves.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity sits close to under-specification for a tool with two undocumented parameters.

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?

With no output schema, no parameter descriptions, and a non-obvious string-encoded array input, the definition leaves too much for the agent to guess. It should state the input encoding and what the returned share is relative to; the annotations cover behavior but not data contract.

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 the description must carry the parameter burden and it does not. The most consequential detail — that 'values' is a JSON-encoded array passed as a string, not a native array — is never mentioned, nor is any constraint on threshold magnitude or pairing between the two parameters. Only the threshold comparison semantics ('strictly above') are clarified.

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 gives a specific verb and resource: it counts observations strictly above a threshold and returns their share as a rate. That is clearly distinguishable from distributional siblings like bpj_series_empirical_cdf or bpj_series_histogram. It stops short of naming or contrasting any sibling explicitly, which keeps it from 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 choose this tool over the many related series statistics in the catalog, and no prerequisites or exclusions. The agent must infer that this is a rate computation rather than, say, a filtered count or a percentile lookup.

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.