Skip to main content
Glama

AutoTasker Hub — China Social Data API

crossref_search

Crossref DOI metadata search: title, authors, DOI, publisher, year, citation count. $0.01 USDC.

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": {
      "query": "<query>"
    },
    "name": "crossref_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful non-schema information — the $0.01 USDC cost (a paid tool) and the categories of metadata returned — but says nothing about what happens on zero results, whether partial matches are returned, or how the citation count is sourced.

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?

Two compact fragments with no filler, front-loading the resource and purpose before the returned fields and the price. The terseness is efficient but borders on telegraphic, dropping connective context about how to phrase a query.

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?

For a simple one-required-parameter lookup with no output schema, the description covers purpose, returned fields, and cost. It is incomplete on the one thing an agent must get right — the accepted format of `query` — and on result-count control via `limit`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with two parameters, so the description must compensate and does not. It never explains whether `query` accepts a DOI string, a title, or free-text syntax, nor does it mention `limit` (default 5, max 20), which the agent can only learn by reading the schema.

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+resource ("Crossref DOI metadata search") and enumerates the field types available (title, authors, DOI, publisher, year, citation count), so an agent can tell it is a scholarly metadata lookup rather than a full-text search. It does not explicitly contrast with sibling academic search tools like pubmed_search or arxiv_search, keeping it 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 Guidelines2/5

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

No guidance on when to prefer this over arxiv_search, pubmed_search, or zenodo_search, and no exclusions or prerequisites. The only implicit cue is 'DOI metadata', leaving the agent to infer that this is for lookups of already-published works rather than literature discovery.

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.