Skip to main content
Glama
konippi

servo-fetch

by konippi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

batch_fetch

Read-onlyIdempotent

Fetch multiple URLs in parallel and extract readable content. Results are returned per URL in completion order, with failures reported inline without stopping the batch.

Instructions

Fetch multiple URLs in parallel and extract readable content. Results are returned as separate content entries, one per URL, in completion order. Failed URLs are reported inline without aborting the batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesURLs to fetch (http/https only). Max 20.
formatNoOutput format: markdown (default) or json
timeoutNoPage load timeout in seconds (per URL). Default: 30
selectorNoCSS selector to extract a specific section
settle_msNoExtra wait in ms after the `load` event. Default: 0. Max: 10000.
max_lengthNoMax characters per URL result. Default: 5000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable behavioral details: parallel execution, completion order, and inline failure reporting. It does not contradict annotations. Could mention network dependency or rate limits, but overall good.

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 sentences, front-loaded with purpose, no redundancy. Every sentence adds value. Extremely concise and well-structured.

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?

Despite no output schema, the description clearly explains the result format (separate entries, completion order, inline failures) and error behavior. It covers key behavioral aspects, making it complete for an agent to use correctly.

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 baseline is 3. The description does not add additional parameter semantics beyond what the schema already provides (e.g., max 20 URLs, default formats). No extra value from description for parameters.

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 clearly states the tool's purpose: 'Fetch multiple URLs in parallel and extract readable content.' It specifies the verb (fetch), resource (multiple URLs), and action (extract content), and distinguishes from sibling tools like fetch (single URL) and crawl (recursive).

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 implies usage for fetching multiple URLs in parallel and describes result ordering and error behavior. However, it does not explicitly state when to use this tool versus alternatives (e.g., single fetch for one URL, crawl for recursive exploration), which would improve guidance.

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