Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Scholarly paper search in one call from Crossref: DOI, title, authors, year, journal, citation count, link for the best

papers_search
Read-onlyIdempotent

Scholarly paper search in one call from Crossref: DOI, title, authors, year, journal, citation count, link for the best matches (q=topic words, count up to 25, from_year optional). For research and citation-checking agents. Pay per call $0.002 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
qNotopic or title words
countNo1 to 25
from_yearNooptional, e.g. 2023
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds something the annotations cannot: a hard cost of $0.002 USDC per call on Base via x402, which is decisive behavioral context for an agent deciding whether to invoke. It stops short of covering result ordering, rate limits, or failure modes.

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 sentences, front-loaded with the resource and return payload, then the commercial terms. The long comma-separated field list in the first sentence is dense but functional. Minimal waste; the truncated repeated title is padding around the description but not part of its body.

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?

With no output schema, the description compensates by enumerating the returned fields, and it discloses the payment model and the first-call auth handshake. For a simple query-and-list tool this is close to sufficient; only result ordering and payment-failure behavior are unstated.

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 all four parameters including the x_payment first-call handshake. The description's parenthetical (q=topic words, count up to 25, from_year optional) largely restates the schema rather than adding format, ranking, or matching semantics. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource ('Scholarly paper search'), names the upstream source (Crossref), and enumerates the returned fields (DOI, title, authors, year, journal, citation count, link). No sibling in the catalog covers scholarly literature, so no in-catalog disambiguation is required and an agent can act on this immediately.

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?

The phrase 'in one call' and 'For research and citation-checking agents' imply the intended context, and the parenthetical sketches how to drive q/count/from_year. However, there is no explicit when-not-to-use guidance, no note on how to handle empty result sets, and no stated alternative for broader or non-Crossref literature. Usage is implied rather than prescribed.

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