Skip to main content
Glama

resolve_handles

Read-onlyIdempotent

Look up the exact passage behind each citation handle and verify whether the handle is genuine, so quotes and citations in an answer can be audited for authenticity.

Instructions

Look up the exact passage behind each handle, and whether the handle is genuine.

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": {
      "handles": "<handles>"
    },
    "name": "resolve_handles"
  }
}

Input Schema

NameRequiredDescriptionDefault
handlesYes

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds a genuinely useful behavioral fact — the call also validates genuineness of handles — but it never says what happens on an invalid handle (error vs. flagged result), which matters for a resolution tool.

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 compact sentence with no wasted words, and the two capabilities (resolve passage, verify authenticity) are front-loaded. It is arguably terse for the amount of unstated semantics, but there is no filler.

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?

An output schema exists, so return-value explanation is not required, and the tool is a simple one-parameter read. Still, the description omits handle format, invalid-handle behavior, and any routing relative to fetch_passages, leaving real gaps for a resolve/validate operation.

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 description coverage is 0%, and the description never defines what a 'handle' is or its expected format, nor that the array can hold up to 50 items. It only implies plural/batch semantics via 'each handle', leaving the single parameter's format largely to the schema's type declaration.

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 uses a specific verb ('look up') and names both the payload ('the exact passage behind each handle') and a second output ('whether the handle is genuine'). That distinguishes it from a plain fetch_passages-style tool, though it does not explicitly name the sibling it differs from.

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 statement, no prerequisite (e.g. 'handles come from search results'), and no exclusion against fetch_passages or search tools. An agent must infer that this is the follow-up step after obtaining handles.

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