OpenPapers

Extract paper claims

extract_paper_claims

Extract source-located facts and claims from a paper URL, persist compatibility heuristics, and report conflicts with prior claims to enable provenance-first research workflows.

Instructions

Persist compatibility heuristic claims, expose canonical v5 facts, and report explicit conflicts with prior claims.

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": {
      "url": "<url>"
    },
    "name": "extract_paper_claims"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

C2.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full transparency burden. It does disclose a key behavioral trait—this tool persists claims, making it a write operation—and says it reports conflicts. However, it leaves important details ambiguous: whether the write is idempotent, what permissions are required, how conflicts are resolved, and what the response contains.

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?

The description is short and contains no obvious filler, but the tripartite verb structure is confusing and not front-loaded around the primary action. Terms like 'v5' are unexplained, so the sentence trades clarity for brevity.

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

Completeness2/5

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

For a side-effecting tool with no annotations, no output schema, and an undocumented parameter, the description is not complete enough. It hints at outputs—exposed facts and reported conflicts—but does not describe return format, call sequence, side effects, or how this tool fits with the large sibling set.

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

Parameters1/5

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

Schema description coverage is 0% and the only parameter, url, is not mentioned in the description at all. The description fails to state what kind of URL is expected—paper page, PDF, DOI, or repository—which is essential for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names specific actions and objects—persisting compatibility heuristic claims, exposing canonical v5 facts, reporting conflicts—so it is not a tautology. However, it never plainly states that the tool extracts claims from a paper, and the phrase 'canonical v5 facts' is unexplained jargon. It also does not distinguish itself from the similarly named extract_paper_facts sibling.

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?

There is no guidance about when to use this tool versus alternatives like extract_paper_facts, verify_claim, or read_paper. The mention of 'prior claims' implies a sequencing requirement, but the description does not state prerequisites, exclusions, or alternative conditions.

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