Skip to main content
Glama
Sign In
deepseek-search

deepseek-search

by BryleXia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

DeepSeek Fetch Page

deepseek_fetch
Read-only

Fetch a single public HTTP/HTTPS page and return its title and Markdown content when search summaries are insufficient for a specific URL.

Instructions

Fetch a single public HTTP/HTTPS page with DeepSeek and return its title and Markdown content. Use for a specific URL when search summaries are insufficient.

  • Not a crawler: for whole-site crawl/map or JS-heavy pages, use a dedicated crawler.

  • Localhost/private/internal addresses and URLs with credentials are rejected.

  • Content is truncated at max_chars.

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
urlYesPublic HTTP/HTTPS URL with a host. Localhost, private IPs, internal hostnames, and URLs with credentials are rejected.
max_charsNoMaximum Markdown characters to return (1000-500000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds real behavior beyond them: SSRF-style rejection of localhost, private IPs, and internal hostnames; rejection of URLs with credentials; and the fact that output is truncated at max_chars. What is missing is rate-limit, auth, or error-surfacing behavior and any mention of redirect handling. Strong, but not exhaustive for a network-fetching tool.

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 leads with a one-sentence statement of what the tool does and returns, then uses three short bullets for exclusions and limits. No sentence repeats the annotations or the schema, and nothing is padded.

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, so the description must state the return shape, and it does: the page title plus Markdown content, with a note that the content can be truncated. Combined with the SSRF constraints, this is enough for an agent to call the tool correctly and to predict what comes back.

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 description coverage is 100%, so the schema already documents both url and max_chars with ranges and defaults. The description's only added meaning is one clause ('Content is truncated at max_chars'), which does not go materially beyond the schema's own description. The baseline of 3 applies when the schema carries the parameter detail.

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 names a specific verb, resource and output: 'Fetch a single public HTTP/HTTPS page with DeepSeek and return its title and Markdown content.' It also separates itself from the only sibling by scoping itself to 'a specific URL when search summaries are insufficient', so an agent can pick between deepseek_fetch and deepseek_search without opening either 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?

It states the trigger condition ('when search summaries are insufficient') and explicitly excludes other cases: 'Not a crawler: for whole-site crawl/map or JS-heavy pages, use a dedicated crawler.' It also spells out a hard precondition (public addresses only, no credentials). Both when-to-use and when-not-to-use are named rather than inferred.

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