Skip to main content
Glama
Sign In
DOI Citation Verifier

DOI Citation Verifier

by tfscharff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

batchVerifyCitations

Read-onlyIdempotent

Verify multiple citations in one call and return a verification status for each, avoiding repeated single-citation checks.

Instructions

Verify multiple citations in a single call. More efficient than calling verifyCitation multiple times. Returns verification status for each citation.

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": "batchVerifyCitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationsYesArray of citations to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv7.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / citations / items / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that a verification status is returned per citation; it says nothing about partial-failure behavior, rate limits, or what statuses are possible, which matters for a network-backed batch tool.

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?

Three short sentences with the batch scope front-loaded and zero filler; each sentence contributes a distinct fact (what it does, why prefer it, what comes back).

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?

There is no output schema, and the description reduces the return value to "verification status for each citation" without enumerating status values or the result shape, which is the main thing an agent needs to consume the response. Adequate on inputs, thin on outputs.

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% for the single `citations` array and every nested field (id, doi, title, authors, journal, year) is documented in the schema. The description adds no parameter-level meaning, so the baseline 3 is correct.

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 verb (verify) and resource (multiple citations) with explicit batch scope, and distinguishes itself from the sibling verifyCitation by contrast. An agent can immediately tell this is the multi-item variant.

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?

"More efficient than calling verifyCitation multiple times" gives a clear condition for choosing this tool over its sibling. It stops short of stating when-not to use it (e.g., single lookups or very large batches with rate limits), but the routing signal is unambiguous.

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

Deploy Server

Other Tools