Skip to main content
Glama

DeepSeek Fetch

deepseek_fetch

Fetch a web page and return its readable content as Markdown, with character-offset paging to retrieve long pages in chunks.

Instructions

Fetch a web page through DeepSeek's Fetch API and return its readable content as Markdown. Supports character-offset paging for 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": {
      "url": "<url>"
    },
    "name": "deepseek_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to fetch (http or https, max 8192 characters).
offsetNoStart offset in characters, for paging through a long page.
max_charsNoMaximum characters to return per call (1000-50000). Default 20000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the output format (Markdown) and the paging behavior via character offsets, but says nothing about authentication, rate limits, timeouts, failure modes (paywalls, non-HTML content), or how truncation is signaled.

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?

Two short sentences, front-loaded with the core action and output format, with the paging capability as a secondary sentence. Nothing is wasted and nothing is buried.

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

Completeness3/5

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

For a simple three-parameter read tool with complete schema coverage and no output schema, the essentials are present. Still, with zero annotations the description could have covered truncation semantics and error behavior, which matter for a paging tool where offset/max_chars can silently cut content.

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 each parameter already documents its type, default, and bounds. The description's mention of character-offset paging adds the intent behind offset and max_chars, but no format details beyond the schema, so the 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 (fetch) and resource (web page), plus the transformation applied (readable content as Markdown). It is clearly distinguishable from siblings like deepseek_search or deepseek_ocr by naming the DeepSeek Fetch API as the mechanism.

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?

Usage is implied by the resource type: fetch one known URL rather than search. However, it never explicitly says when to prefer deepseek_search or deepseek_ocr, nor does it state prerequisites such as requiring a fully qualified public http/https URL.

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