graphrag-ts-pg

integrity_paper_status

Look up one paper by DOI or OpenAlex id and return its identity (title, year, venue) plus every retraction record the graph holds for it, each with its source and source tier: A is an official registry, B an authoritative index, C an aggregator. Use it to check whether a paper is retracted and which sources assert it; use retraction_propagation to judge whether that retraction reaches a specific citing paper. Free in the public tier. Returns: paper identity and statuses[] with source, source_tier, is_retracted, retraction_date and source_uri; abstention_reason when the paper is not in the snapshot.

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

Input Schema

Name	Required	Description	Default
`doi`	No	DOI of the paper, e.g. 10.1016/S0140-6736(97)11096-0. Provide exactly one of doi or paper_id.
`paper_id`	No	OpenAlex work id, e.g. W2117847125. Provide exactly one of doi or paper_id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / doi

Added value: +{
+  "description": "DOI of the paper, e.g. 10.1016/S0140-6736(97)11096-0. Provide exactly one of doi or paper_id.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / paper_id

Added value: +{
+  "description": "OpenAlex work id, e.g. W2117847125. Provide exactly one of doi or paper_id.",
+  "minLength": 1,
+  "type": "string"
+}

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it defines the A/B/C source-tier semantics, states the cost model ('Free in the public tier'), and discloses the non-happy path ('abstention_reason when the paper is not in the snapshot'). That is exactly the kind of behavior an agent cannot infer from the schema.

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

Conciseness5/5

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

Front-loaded with the action and inputs, then purpose, then cost, then return shape. Every clause carries information (tiers, sibling routing, abstention) and there is no filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by spelling out the return payload field-by-field (identity, statuses[] with source, source_tier, is_retracted, retraction_date, source_uri). With the tier legend and abstention case also covered, an agent has everything needed to call and interpret this tool.

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 coverage is 100% and both parameters already document the 'provide exactly one of doi or paper_id' constraint with example formats. The description only restates the DOI/OpenAlex id duality, adding no syntax or disambiguation beyond the schema, so baseline 3 applies.

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 ('Look up one paper by DOI or OpenAlex id') and enumerates exactly what is returned: identity (title, year, venue) plus every retraction record. It is unmistakably distinct from the sibling retraction_propagation, which is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit when-to-use ('check whether a paper is retracted and which sources assert it') and an explicit alternative with its own condition ('use retraction_propagation to judge whether that retraction reaches a specific citing paper'). The routing decision is fully resolved in the description.

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

All graphrag-ts-pg tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?