Skip to main content
Glama

Midrank percentiles

bpj_series_midrank_percentiles
Read-onlyIdempotent

Give each observation the fraction below it plus half the fraction tied with it.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety behavior is covered. The description adds the core computation formula, which is useful behavioral context, but it does not describe output shape, tie handling beyond the formula, or input parsing requirements.

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, front-loaded sentence with no wasted words. It immediately conveys the mathematical rule without preamble or redundancy.

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 simple one-parameter statistical transform with annotations and no output schema, the description gives the essential computation but omits input format details and output structure. An agent can likely infer the input from the schema title, but the definition is not fully self-contained.

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 parameter 'values' has 0% schema description coverage; the schema only provides a title 'Number array (JSON)' and maxLength. The description says 'each observation' but does not explain that the input must be a JSON-encoded array of numbers or clarify the format, so it does not compensate for the missing schema documentation.

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 statistical operation: assigning each observation a value based on the fraction below it plus half the tied fraction. This is a clear definition of midrank percentiles, though it lacks an explicit verb like 'compute' and does not name sibling alternatives such as empirical CDF or quantile.

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 alternatives like bpj_series_empirical_cdf, bpj_series_quantile, or bpj_series_dense_rank. The description only defines the calculation, leaving the agent to infer appropriate contexts.

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.