Skip to main content
Glama

check_references

Read-onlyIdempotent

Verify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues. Results may be cached for up to six hours and usage may be logged; the bibliography is not published or added to an account. With a CiteMe API key, references matched to a record may also be sent to Typesafe for a second identity check, under zero data retention.

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": {
      "text": "<text>"
    },
    "name": "check_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw bibliography text (one reference per line, or a full references section)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, and the description goes well beyond them: six-hour caching, usage logging, no publication or account storage, and an opt-in second identity check sent to Typesafe under zero data retention. That is exactly the extra auth and data-handling context annotations cannot convey.

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 front-loaded sentences: the first states what it does and returns, the second packs caching, logging, storage, and the API-key branch without wasted words. Every clause carries information.

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?

No output schema exists, and the description sufficiently characterizes the return values (match status, identifiers, citation issues) plus data-handling caveats. For a single-parameter read-only tool this is nearly complete; only the sibling routing story is missing.

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 100% and the single parameter is fully documented in the schema (raw bibliography text, one reference per line, length bounds). The description adds nothing about the input format, so the baseline 3 is appropriate.

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 ('Verify a user-provided bibliography against scholarly sources') and lists the concrete outputs (match status, identifiers, citation issues). It does not explicitly distinguish itself from the siblings format_citation or search_citations, so it falls 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 Guidelines3/5

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

The purpose implies when to reach for it, and the API-key/Typesafe sentence is a useful trigger condition, but there is no explicit when-to-use versus format_citation or search_citations and no when-not guidance. Usage is inferable rather than spelled out.

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