Skip to main content
Glama
mcp-server-starter-sample

mcp-server-starter-sample

by DingXinPro

fetch_url

Fetches up to 200 KB of text from allowlisted HTTPS URLs and blocks private networks, supporting controlled external content retrieval.

Instructions

Fetch an allowlisted https URL and return up to 200 KB of text. Private networks are blocked.

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": "fetch_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits beyond the schema: a 200 KB response cap, an allowlist gate, and SSRF-style blocking of private networks. It does not say whether truncation is silent or signalled, how non-text or HTML content is handled, what error surfaces on a blocked URL, or whether auth headers can be supplied.

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 with zero filler; the capability and its size limit come first, and the security constraint is front-loaded rather than buried. Every clause carries information an agent needs.

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

Completeness4/5

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

For a one-parameter fetch tool with no output schema and no annotations, the description covers the essentials: what it returns (text), how much (200 KB), and what is refused (non-https, non-allowlisted, private networks). The remaining gap is failure signaling — the agent can't tell what a blocked or truncated response looks like.

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?

There is one parameter and the schema describes it only as a bare string at 0% coverage. The description compensates by constraining it to an https, allowlisted URL, which is genuine meaning the schema doesn't carry. It still says nothing about accepted formats for that string (query strings, fragments, redirects).

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 and resource (fetch a URL) and immediately bounds the operation with concrete modifiers: allowlisted, https, up to 200 KB. An agent knows exactly what the tool does. It doesn't name or contrast with the sibling sqlite_query, but the domains are so different that differentiation is implicit rather than stated.

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?

The definition implies when this applies (retrieving web/https content) and encodes hard preconditions the agent must respect — the URL must be https and must be on the allowlist. What it omits is any explicit statement of when not to use it or what to do instead for non-allowlisted or private-network targets.

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