Skip to main content
Glama

Get citation scan detail

get_citation_scan
Read-onlyIdempotent

One Citation Management scan in detail: each listing found (site, address, match class, accuracy and which fields matched or differed). Use list_citation_scans for scan ids.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_citation_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that by describing the shape of the payload returned for a single scan, which matters given there is no output schema. Auth requirements and error behavior (e.g., unknown scan_id) are not mentioned.

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?

Two sentences, front-loaded with the resource and its scope, followed by the prerequisite routing hint. The parenthetical field list is dense but every element describes what the caller receives, so nothing 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?

For a simple one-parameter read tool with no output schema, the description covers both the input source and the return contents, which is enough to call it correctly. Only minor edges — failure modes and whether results are paged — remain unspecified.

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% for the single scan_id parameter, so the description must carry the load, and it partially does by pointing to list_citation_scans as the source of ids. It adds no information about the uuid format or what happens with an invalid or foreign id.

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 resource ('One Citation Management scan in detail') and enumerates the returned content (site, address, match class, accuracy, field diffs), which clearly separates it from the plural list_citation_scans sibling. The retrieval verb is implied by the name rather than stated, keeping it just 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use list_citation_scans for scan ids' gives an explicit alternative for the prerequisite step, so an agent knows how to obtain the required scan_id. It does not cover when-not to use this tool or contrast with request_citation_scan, but the context it does provide is concrete.

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.

Resources