Skip to main content
Glama
Sign In
io.github.VelvetSP/web-retrieval-mcp

io.github.VelvetSP/web-retrieval-mcp

by VelvetSP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

research_paper

Read-only

Retrieve a paper by ID (paperId or arXiv ID) to get metadata; include a query to return full-text passages for verifying claims, methods, or results before relying on it.

Instructions

Inspect ONE paper from the Research Index by id (a paperId, or an arXiv id like "arxiv:2606.01509"). Without query → metadata (title, authors, categories, dates, abstract). With query → ALSO the top full-text passages answering it — use this to VERIFY a paper actually contains a method/dataset/result before relying on it.

Args: paper_id: paperId or primaryId ("arxiv:NNNN.NNNNN") from research_papers. query: optional question; when set, returns claim-verification passages.

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": {
      "paper_id": "<paper_id>"
    },
    "name": "research_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
paper_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description explains exactly what happens without a query (metadata fields listed) and with a query (top full-text passages). This gives the agent a clear model of the tool's conditional behavior.

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?

The description is compact, front-loaded, and every line adds information. The behavior is summarized first, followed by concise parameter details. No filler or redundant restatement.

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?

With a readOnlyHint, an output schema, only two parameters, and a clear explanation of both input formats and output modes, the description fully equips an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the full semantic load. It does: paper_id is explained as a paperId or primaryId with an example format, and query is described as an optional question returning verification passages.

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?

The description states a specific verb ('Inspect'), a specific resource ('ONE paper from the Research Index'), and the exact accepted identifiers. It differentiates from siblings like research_papers by emphasizing single-paper retrieval and the optional query mode.

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

Usage Guidelines4/5

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

The description explicitly says when to use the tool: to VERIFY that a paper contains a method/dataset/result before relying on it. It implies research_papers is the source for finding paper IDs but does not explicitly state exclusions or alternatives beyond this.

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

Deploy Server

Other Tools