Skip to main content
Glama

Linearly interpolated quantile

bpj_series_quantile
Read-onlyIdempotent

Evaluate a requested quantile by interpolation at position (n - 1) times p.

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>",
      "p": "<p>"
    },
    "name": "bpj_series_quantile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pYes
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 read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds the concrete interpolation formula, which is genuine algorithmic context, but it omits edge-case behavior (empty or single-element series, whether values are sorted internally, p ties) and says nothing about the returned shape.

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 zero filler and no repetition of the title. It is efficient, though its brevity leaves the tool under-specified rather than crisp.

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, the description should say that a scalar quantile value is returned, and with 0% parameter coverage it should explain the JSON-string encoding of 'values'. Neither is present, so an agent calling this stateless math tool must guess on both input format and return value.

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 load, and it largely does not. It references the quantile fraction only obliquely and never explains that 'values' is a JSON-encoded number array supplied as a string (maxLength 12000) rather than a native array, which is the single most error-prone aspect of calling this tool.

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 verb and resource ('Evaluate a requested quantile') and pins down the exact estimator ('interpolation at position (n - 1) times p'), which implicitly distinguishes it from siblings such as bpj_series_midrank_percentiles or bpj_series_empirical_cdf. It does not, however, state the input domain or return type, so an agent still has to infer basic context.

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 at all: nothing says to pick this over the rank-based or CDF-based percentile siblings, and no preconditions (e.g., values must be numeric and ordering assumptions) are given. The agent has only the method name to route on.

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.