Skip to main content
Glama

Empirical CDF steps

bpj_series_empirical_cdf
Read-onlyIdempotent

List each distinct observation and the empirical probability at or below 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_empirical_cdf"
  }
}

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the output shape (distinct value + cumulative probability), which matters because no output schema exists, but it says nothing about ordering of the listed steps, how ties/duplicates are collapsed, or output format (pairs vs. arrays).

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?

One sentence, front-loaded with the verb and the resource, with zero filler. There is nothing to trim.

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?

With no output schema the description must carry the return shape, and it does so adequately by describing value/probability pairs. However, for a tool whose only input is a JSON-encoded string, the omission of input encoding and of step ordering leaves the definition short of what an agent needs to call it correctly.

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% for the single required parameter, and the description does not compensate at all. Critically, the parameter is typed as a string titled 'Number array (JSON)' with a 12000-character limit, so the agent needs to know it must pass a JSON-encoded array rather than a bare number or CSV, and the description never says this.

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 ("List") and a precise resource (each distinct observation plus its empirical probability at or below it), which is exactly the ECDF definition and implicitly contrasts with the 'at or above' logic of siblings like bpj_series_exceedance. It does not explicitly name or rule out any sibling, so it stops short of full differentiation.

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, no exclusion conditions, and no pointer to alternatives such as bpj_series_histogram or bpj_series_quantile for related distribution summaries. The agent must infer the use case entirely from the mathematical term.

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.