SiteCheck Web Intel

Crossref DOI lookup: title, authors, journal, publication

search_crossref_academic_paper

Read-only

Crossref DOI lookup (public REST API, no key): title, authors, journal, publication date, cited-by count, publisher and link for one paper. Unknown DOIs return 404. Related tools on this server, for a different need: search_crossref when you need Crossref works search: DOI, title, type, container, year. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "doi": "<doi>"
    },
    "name": "search_crossref_academic_paper"
  }
}

Input Schema

Name	Required	Description	Default
`doi`	Yes	DOI such as 10.1038/nature12373

Output Schema

Name	Required	Description	Default
`doi`	No
`url`	No
`type`	No
`title`	No
`source`	No
`authors`	No
`citedBy`	No
`journal`	No
`checkedAt`	No
`published`	No
`publisher`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that this is a public REST API with no key, that unknown DOIs return 404, that there is a per-call cost, and that failed calls are not charged. Those are important behavioral details for an agent deciding whether and how to invoke it.

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?

The description is front-loaded with the purpose and then efficiently covers the 404 behavior, the sibling alternative, and pricing. It is dense but not bloated; the pricing sentence is necessary and the related-tool sentence is clearly marked as a different need.

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?

For a single-parameter, read-only external lookup, the description covers the key operational facts: no API key, failure behavior, cost and payment mechanism, and the sibling alternative. An output schema exists, so the description does not need to explain return-value structure in more detail.

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 only parameter already has an example DOI in the schema. The description reinforces that the lookup is for one paper but adds no syntax or formatting details beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb/resource: 'Crossref DOI lookup' for 'one paper', and lists the exact metadata returned. It also names search_crossref as a different need, so an agent can distinguish this from its sibling 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?

It makes the core usage condition clear: use this for a single DOI lookup and use search_crossref for Crossref works search by DOI, title, type, container, or year. It does not explicitly state when not to use it beyond the 404 case, but the alternative routing is clear.

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

All SiteCheck Web Intel tools Inspect

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

Need Help?