Skip to main content
Glama

Rank a permutation

bpj_discrete_permutation_rank
Read-onlyIdempotent

Rank a permutation of distinct integers in zero-based lexicographic 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_discrete_permutation_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the meaningful conventions the annotations cannot carry: zero-based indexing, lexicographic ordering, and the distinct-integer constraint. It does not say what happens with duplicates or what the result looks like, which keeps it at a 3.

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 tight clause with the qualifiers front-loaded and no filler. It is efficient, though some of that brevity is under-specification rather than economy — the space saved could have documented the input encoding.

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 carries the burden of explaining that the return value is a zero-based integer index, which it only hints at through the word "rank". Combined with the undocumented string encoding for the required parameter, an agent cannot confidently construct a call or interpret the result from this definition alone.

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 typed as "Distinct integer array" with a 1024-char limit — the crucial ambiguity is the encoding (comma-separated? space-separated? JSON?). The description only reinforces "distinct integers" and never resolves the serialization format, so the agent is left guessing how to build the argument for the one required parameter.

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?

"Rank a permutation of distinct integers in zero-based lexicographic order" gives a specific verb (rank) plus resource (permutation) and even pins down the ordering convention, so an agent knows exactly what computation happens. It does not differentiate itself from siblings such as bpj_series_dense_rank or explain how its ranking differs from theirs, so it stops short of 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 when-to-use guidance, no statement of preconditions (e.g. values must be distinct), and no routing to or away from alternatives like bpj_series_dense_rank. The only signal is implicit in the word "permutation".

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.