Skip to main content
Glama
Native Research MCP

Native Research MCP

by pipiwego

deepseek_read_url

Read-only

Read a public web page for a specific research question and focus extraction on relevant evidence; use new focus queries to extend earlier findings when long pages are truncated.

Instructions

Read a public page for a specific question. A new focus extends earlier evidence. Native tools can truncate long pages.

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": {
      "research_id": "<research_id>",
      "parent_revision": "<parent_revision>",
      "gap": "<gap>",
      "url": "<url>",
      "focus": "<focus>"
    },
    "name": "deepseek_read_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapYes
urlYes
focusYes
refreshNo
research_idYes
parent_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, non-idempotent, and non-destructive, so safety is covered. The description adds genuine value with the truncation caveat (why to use this over a native fetch) and the incremental 'extends earlier evidence' model. It omits critical behavior: that calls are tied to a research session and a parent_revision, and what happens with refresh.

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?

Three short sentences with the core action front-loaded and no filler. The wording is economical, though sentences two and three are terse to the point of being cryptic rather than explanatory.

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?

This is a 6-parameter, 5-required, session-structured tool with zero schema description coverage and no output schema. The description should explain how research_id/parent_revision determine state and what the read returns; it addresses none of this, leaving an agent unable to construct a valid call from the description alone.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must carry the meaning and largely does not. 'Focus' and 'specific question' loosely gesture at focus/gap, but research_id, parent_revision, refresh, and the page url are never explained, even though 5 of the 6 parameters are required and the revision chaining is non-obvious.

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?

States a specific verb+resource: 'Read a public page for a specific question.' An agent can tell this fetches page content rather than searching. It does not name deepseek_search or explain the boundary between searching and reading, so it stops short of the 5-level sibling differentiation.

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?

'A new focus extends earlier evidence' implies the tool is used inside an ongoing research session to follow up on prior findings, and 'Native tools can truncate long pages' implies a reason to prefer it. But there is no explicit when-not guidance, no mention of required prerequisites (research_id/parent_revision chaining), and no named alternative.

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