Skip to main content
Glama

Dense ranks with ties

bpj_series_dense_rank
Read-onlyIdempotent

Assign consecutive ranks to distinct ascending values and preserve input order.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine semantics beyond that: ties collapse to the same consecutive rank, values are ordered ascending, and output preserves input order; however it says nothing about the expected input encoding or the returned shape, which matters for a transform tool with no output schema.

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?

One short sentence with the ranking rule front-loaded and no filler; every clause carries meaning. It is efficient but perhaps too terse for the amount of undocumented behavior attached to a JSON-string parameter.

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?

There is no output schema, so the description carries responsibility for describing the return value, which it only implies via 'preserve input order'. Combined with a fully undocumented parameter, an agent can guess the call correctly but not the exact input format or output shape.

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% and the single parameter is a string carrying a JSON number array with a 12000-character cap. The description never mentions that the input must be a JSON-encoded array, nor any limits, edge cases (empty series, non-numeric entries), or how ties are detected, so it does not compensate for the schema gap.

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?

States a specific verb and resource ('assign consecutive ranks to distinct ascending values') plus an output-order guarantee, which pins down dense-ranking semantics precisely. It does not name or distinguish itself from near-siblings such as bpj_discrete_permutation_rank or bpj_series_midrank_percentiles, so an agent must infer the difference from the names alone.

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 exclusions, and no reference to any alternative ranking tool. The only implied guidance is the bare notion of ranking, which is covered by several siblings, leaving the agent to guess which ranking variant to call.

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.