Skip to main content
Glama

Agent Exchange store

papers_references

$0.005 via x402: What a paper cites: its reference list by DOI (Crossref: up to 100 entries with DOI, title, author, year, journal as deposited) and the count of works citing it; for arXiv ids, the referenced OpenAlex work ids. Pay 0.005 USDC through https://store.agentexchange.work/gw/papers/references?id=10.1038/s41586-021-03819-2 Via the Agent Exchange store gateway; settled by Coinbase.

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": {
      "id": "<id>"
    },
    "name": "papers_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it discloses the key trait: this is a paid call ($0.005 via x402, USDC through the Agent Exchange gateway, settled by Coinbase), with the schema noting the price is returned when no payment is supplied. It adds real context beyond structured fields, though it stops short of error/failure or rate-limit behavior.

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

Conciseness3/5

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

Purpose is front-loaded with 'What a paper cites,' which is good. However, the payment/marketing tail (example URL, gateway name, 'settled by Coinbase') is somewhat verbose and mixes promotional detail with essential information, diluting an otherwise compact definition.

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

Completeness4/5

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

There is no output schema, so the description must describe returns, and it does: reference entries with DOI, title, author, year, journal, a citing-works count, and OpenAlex ids for arXiv. Combined with the payment-flow explanation, it is nearly complete for an agent to call it correctly.

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

Parameters4/5

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

Although schema coverage is 100%, the schema's descriptions are literally 'id' and a payment placeholder, so they add no meaning. The description compensates by clarifying that the id is a DOI (with a concrete example) or an arXiv id, which is genuine semantic value beyond 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?

The description states a specific verb+resource: it returns what a paper cites (reference list by DOI) plus citing-works count, and OpenAlex work ids for arXiv ids. It is far more specific than a tautology and the scope is clear. It does not explicitly differentiate itself from siblings like papers_paper or papers_verify, keeping it at 4 rather than 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?

The description communicates the use case (fetching a paper's references/citations) but gives no when-to-use vs. when-not guidance and never names alternatives such as papers_paper or papers_search. An agent must infer which sibling to call.

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