Skip to main content
Glama

rank_passages

Ranks passages by relevance to a question and returns the top_k most relevant first, each with its index and a 0-1 relevance score, plus an ANSWER or SEARCH decision.

Instructions

Rank passages by relevance to question (the chopper used as a reranker: on a held-out 8-language set it ranks within ~1 nDCG point of bge-reranker-v2-m3 at the same speed). Returns the top_k passages, most relevant first, with their index and relevance (0..1), plus decision ANSWER / SEARCH.

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": {
      "question": "<question>",
      "passages": "<passages>"
    },
    "name": "rank_passages"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNo
passagesYes
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the output shape (ordered top_k with index and 0..1 relevance, plus decision) and even a quality/speed benchmark, but it says nothing about input limits (passage count, length), determinism, latency/cost, or failure behavior — gaps that matter for a tool whose whole job is scoring.

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?

Two sentences, front-loaded with the action and followed by the return contract. The benchmark comparison is somewhat promotional but is plausibly useful for trusting the ranking quality; nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly spells out the return values and ordering, and it covers the decision output. Missing pieces are input limits and error behavior, which keep it short of fully complete for a 3-parameter scoring tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains what all three parameters mean in context (question, passages, top_k as the number returned), but adds no constraints such as maximum passages, string length limits, or what happens when fewer than top_k passages are supplied.

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: rank `passages` by relevance to `question`. The parenthetical clarifies its role as a reranker (as opposed to the sibling chopper tools), which gives an implicit distinction, though no sibling is named directly.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The mention that the result includes a decision ANSWER / SEARCH hints that this is a gating step, but the agent must infer that rather than being told.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools