Skip to main content
Glama
Sign In

Citation Verification

by io.github.guptaprakhariitr
OverviewDiscussionsAdmin

cite_check

Verify that one or more cited URLs (a) resolve, (b) match the cited claim text, and (c) aren't retracted. Useful when an LLM produced inline citations and you want to confirm they're real and on-point. Pass DOIs directly (e.g. '10.1038/nature12373') or full URLs. Up to 25 per call.

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": {
      "citations": "<citations>"
    },
    "name": "cite_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Despite no annotations, the description discloses the three verification actions, the optional claim parameter yielding a match_score, and the batch limit. It implies a read-only operation without explicitly stating it.

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 efficient sentences followed by a concise list of checks. Every clause adds value, no redundancy, and the critical purpose is immediately clear.

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?

Lacks details on the full return format (e.g., whether it returns per-item status, error handling, or response fields beyond match_score). For a tool with no output schema, this leaves agents guessing about the response structure.

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

Parameters4/5

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

The description adds meaningful context beyond the schema: explains that DOIs are accepted, that claim elicits a match_score, and caps at 25. Schema descriptions already cover param roles, so this is additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool verifies cited URLs against three criteria (resolve, match claim, not retracted). This specific verb-resource combination distinguishes it from siblings fact_check and source_freshness.

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?

Provides a concrete use case ('when an LLM produced inline citations') and input format guidance (DOIs or URLs, up to 25). Does not explicitly mention when not to use, but the context is clear.

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

All Citation Verification toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources