Skip to main content
Glama

Check reference

check_reference
Read-onlyIdempotent

Whether a reference resolves to a real work. Use when an answer is about to cite a paper. Give a DOI, arXiv id, PMID or reference as written. Answers found, confirm (with the reason), not found in the named sources on a date, or couldn't check. A not-found is not proof a work was never published.

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": {
      "identifier": "<identifier>"
    },
    "name": "check_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesThe reference to check: a DOI (10.x/y, doi:10.x/y or a doi.org URL), an arXiv id, a PubMed ID (PMID: 12345678), or the reference as written (a title or a full citation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / identifier / description
      Previous value: -"The reference to check: a DOI (10.x/y, doi:10.x/y or a doi.org URL), an arXiv id, or the reference as written (a title or a full citation)"New value: +"The reference to check: a DOI (10.x/y, doi:10.x/y or a doi.org URL), an arXiv id, a PubMed ID (PMID: 12345678), or the reference as written (a title or a full citation)"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the description's job is to explain outcomes — and it does: the four answer states (found, confirmed with reason, not found in the named sources on a date, couldn't check) are spelled out. It further discloses the important epistemic caveat that a not-found result is not proof of non-existence, which is exactly the kind of context an agent needs and cannot get from annotations.

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?

Five short sentences, front-loaded with the core predicate followed by the trigger condition, input expectation, outcome states, and caveat — no sentence is redundant or padded.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one parameter and no output schema, the description carries the full burden of describing return states and it does so explicitly, including the asymmetry of a negative result. Nothing an agent needs in order to call and interpret this tool 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 coverage is 100% and the single parameter already enumerates accepted identifier forms (DOI, arXiv id, PMID, or the reference as written). The description's "Give a DOI, arXiv id, PMID or reference as written" largely restates that schema text, so it adds little beyond convenience. Baseline 3 applies.

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?

States a specific verification predicate ("Whether a reference resolves to a real work") with a concrete resource type and scope, which an agent can readily separate from listing-style siblings such as references_of or what_cites. The purpose is unambiguous without opening the schema.

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?

Gives an explicit trigger condition: "Use when an answer is about to cite a paper." That is a clear when-to-use context, but no when-not-to-use guidance or named alternatives (e.g., retraction_listing) are offered, so it stops short of full routing guidance.

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.