Skip to main content
Glama

Research data (x402)

papers_verify

$0.003 via x402: Does this reference exist? Give a title (and optionally year and first author): the closest real work in Crossref with a match score 0 to 1, its DOI and citation count, or no match. Built for agents that must not cite papers that do not exist. Pay 0.003 USDC through https://store.agentexchange.work/gw/papers/verify?title=Self-Consistency+Improves+Chain+of+Thought+Reasoning+in+Language+Models&year=

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": {
      "title": "<title>"
    },
    "name": "papers_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoyear
titleYestitle
authorNoauthor
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.7/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 burden and does well: it discloses the cost ($0.003), the x402/USDC payment rail, the endpoint, and the fact that payment is required to get the real answer (mesh with x_payment). It also describes the output shape. It doesn't cover failure modes or rate limits, so not a 5.

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?

It is front-loaded with pricing and purpose, but the price is stated twice ('$0.003 via x402' and 'Pay 0.003 USDC'), and the full example payment URL with an embedded long title consumes substantial space relative to its informational value.

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?

For a tool with no annotations and no output schema, the description is largely self-sufficient: it explains the cost, payment flow, inputs, and the returned fields. Only edge-case behavior (invalid input, network/timeout handling) is unaddressed, a minor gap given the tool's narrow scope.

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?

Schema coverage is 100% but the schema's own param descriptions are trivial ('title', 'year', 'author'). The description elevates them, clarifying title is required, that year and author are optional, and that the author should be the first author, which adds real semantic value over 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 (verify existence) and resource (a paper reference) and even specifies the return payload: closest Crossref match with a 0–1 score, DOI, and citation count, or no match. It is distinguishable from papers_search/papers_paper by being a boolean-ish existence check, though it doesn't name those siblings for contrast.

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?

It gives a usage context ('Built for agents that must not cite papers that do not exist'), which implies when to reach for it. However, it offers no explicit when-not conditions and never contrasts with the nearby papers_search, papers_paper, or papers_references tools, so routing between them is left to inference.

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