Skip to main content
Glama

Find a DOI's record or search bibliographic records

doi
Read-only

A DOI's bibliographic record from Crossref (title, authors, journal, publisher, date, type, citation count, license), or the best matches for a citation-style search (max 10). An unknown DOI answers 404, not charged. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doi"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOr a citation-style search
doiNoDOI, e.g. 10.1038/nature14539
limitNoMatches for q, 1 to 10 (default 5)

Output Schema

NameRequiredDescriptionDefault
countNo
worksNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description sensibly spends its words elsewhere: unknown DOIs answer 404 and are not charged, successful calls cost $0.002, payment is x402 USDC across Base, Solana and 10 more networks. That payment and error-charging behavior is genuinely non-inferable and valuable. It stops short of rate limits, latency, or what happens on partial-match searches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what you get back before the error/pricing caveats. The parenthetical field list (title, authors, journal, publisher, date, type, citation count, license) is partly redundant with the existing output schema and is the one stretch that doesn't fully earn its place.

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?

Pricing, charge-on-success-only, and 404 semantics make this complete on the commercial side, and the output schema covers return values. The gap is the dual-mode contract: with zero required parameters, an agent gets no rule for combining q and doi, or for what a bare call returns.

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%, so the schema already documents q, doi and limit. The description adds only 'max 10' matches and that q drives citation-style lookup — the limit range (1-10, default 5) and the DOI example are already in the schema. 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?

The description names the resource precisely — 'A DOI's bibliographic record from Crossref' — and enumerates the exact fields returned, plus a second mode ('best matches for a citation-style search'). 'Crossref' scopes it against sibling corpora like arxiv or books, though it never explicitly points at an alternative. The lack of a leading verb is offset by two clearly delineated operations.

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?

Usage is only implied through the parameters: supply a DOI for a record, or 'q' for a citation-style search. There is no explicit statement of when to choose this over arxiv, books, or other bibliographic siblings, and no guidance on what happens if both or neither of q/doi are supplied (zero required parameters).

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