Skip to main content
Glama

fetch

Retrieve web page text from multiple URLs by automatically trying a DeepSeek API and then static, dynamic, or stealth containers as fallbacks.

Instructions

Fetch page text. Tries the DeepSeek Fetch API first (no container), then a static -> dynamic -> stealth container ladder.

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": {
      "urls": "<urls>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNojson
tierNoauto
urlsYes
text_limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It usefully discloses the escalation ladder (DeepSeek API first, then static/dynamic/stealth containers) but omits failure behavior, permission or auth needs, rate limits, and what the stealth tier implies.

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?

Two sentences, front-loaded with purpose, with no filler. The parenthetical 'no container' and ladder notation are compact but slightly cryptic.

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?

With no annotations, no output schema, and 0% parameter description coverage, the description is too thin for a four-parameter tool. It covers purpose and fallback strategy but leaves parameter meaning, output shape, and usage boundaries unexplained.

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%, and the description names none of the four parameters (urls, out, tier, text_limit). It only indirectly illuminates the tier enum by describing the static -> dynamic -> stealth ladder, leaving the other parameters undocumented.

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?

The description gives a specific verb and resource ('Fetch page text'), so the agent knows the tool retrieves page content. It does not explicitly contrast with the sibling 'search' tool, so it falls short of full 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 Guidelines2/5

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

It explains the internal fallback order but gives no when-to-use or when-not-to-use guidance and never mentions the sibling search tool. An agent must infer that this is for retrieving a known page rather than discovering pages.

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