Skip to main content
Glama

omniseek_paper_enrich

Read-only

Retrieves open-access PDF links, citation counts, and retraction status for a paper by DOI or arXiv ID, covering details that standard search does not provide.

Instructions

Use WHEN you need ONE paper's open-access full-text PDF, retraction / integrity status, or citation count: signals omniseek_search / field_skeleton do NOT give cleanly.

Tool name: omniseek_paper_enrich (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_paper_enrich".

Args: ids: DOIs and/or arXiv ids (not OpenAlex W-ids).

Returns {results: [{id, kind, doi, is_oa, oa_status, oa_by, pdf_url, oa_url, citation_count, integrity: {retracted, notices}}]}; an unrecognized id comes back as {id, error}. is_oa false = no free copy known to Unpaywall (still try omniseek_read on the DOI URL); retracted null = not checked; citation_count null = backend unreachable. Read pdf_url with omniseek_read for the full text. More: omniseek docs/TOOLS.md, omniseek_paper_enrich.

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": {
      "ids": "<ids>"
    },
    "name": "omniseek_paper_enrich"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

With readOnlyHint=true already covering safety, the description still adds real behavioral detail: null semantics (retracted null = not checked, citation_count null = backend unreachable), the {id, error} shape for unrecognized ids, and that is_oa false means Unpaywall has no known free copy rather than no copy existing. That is genuinely valuable beyond the annotations; only a note on rate limits or batching is missing.

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?

Front-loaded WHEN clause, then Args, Returns, and fallback notes in a scannable block structure; nearly every line carries information. The framework boilerplate about tool-name prefixing and ToolSearch is inherited noise, and the Returns block is dense enough to need re-reading.

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, but the description documents the return object field-by-field and explains the error path and null cases. For a one-parameter read tool, nothing an agent needs to call it correctly or interpret results is missing.

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 0% (a bare array of strings titled 'Ids'), so the description carries the full burden and does so by specifying accepted identifier types and an important exclusion: DOIs and/or arXiv ids, not OpenAlex W-ids. It stops short of giving concrete format examples for arXiv ids (prefix conventions), leaving a small ambiguity for malformed input.

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?

Opens with a specific use-case verb phrase ('need ONE paper's open-access full-text PDF, retraction / integrity status, or citation count') and explicitly contrasts with omniseek_search and omniseek_field_skeleton, which it says do NOT give these cleanly. An agent can distinguish this from the lookup siblings without opening any schema.

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?

States the triggering condition ('Use WHEN...'), names the alternatives it replaces, and adds follow-up routing: if is_oa is false, still try omniseek_read on the DOI URL, and read pdf_url with omniseek_read for full text. This is explicit when-to-use plus what-to-do-next, not just context.

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