Skip to main content
Glama
Sign In
Web Intel MCP

Web Intel MCP

by ArceeDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

read_url

Read-onlyIdempotent

Fetch a web page and return its main content as clean Markdown, stripping navigation, ads, and cookie banners for easier reading or processing.

Instructions

Fetch a web page and return its main content as clean Markdown (nav, ads and cookie banners removed).

Args: url: Page URL (https:// is assumed when no scheme is given). max_chars: Cap on returned markdown length (default 20000, max 100000).

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

Input Schema

NameRequiredDescriptionDefault
urlYes
max_charsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, open-world), and the description adds genuinely new behavior: boilerplate removal (nav/ads/cookie banners) and a hard truncation ceiling of 100000 characters. It omits known real-world caveats such as JS-rendered content, paywalls, or redirect handling, which keeps it short of a 5.

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?

The core behavior is front-loaded in one sentence, followed by a compact Args block; there is no filler. The max_chars default of 20000 is repeated from the schema, a minor redundancy.

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?

With only two parameters, an existing output schema, and annotations covering the safety profile, the description supplies everything an agent needs to call it correctly: what it returns, how content is cleaned, and truncation limits. Remaining unknowns (rendering, auth walls) are edge cases rather than invocation blockers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does it: 'url' explains that https:// is assumed when no scheme is given, and 'max_chars' states both the default and the 100000 maximum. Both parameters gain meaning that is absent from the schema.

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+resource ('Fetch a web page') and states the output shape ('main content as clean Markdown'), which implicitly separates it from siblings like extract_links and page_metadata. It never names an alternative, so the differentiation must be inferred rather than read directly.

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 only implied: an agent can infer this is the tool for reading page body text, but there is no explicit when-to-use, when-not-to-use, or routing to page_metadata/extract_links for structured data. No prerequisites or failure conditions are mentioned.

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