Skip to main content
Glama

LinkVet

Read a web page as clean Markdown (with token count)

read_page
Read-onlyIdempotent

Fetch a public URL and return its main content as clean Markdown (navigation, scripts, footers removed; links absolutized), plus title, final URL and an estimated token count, truncated to max_tokens. Cheaper on context than raw HTML.

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_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
max_tokensNoTruncate output to about this many tokens (default 8000, max 50000)
include_linksNoKeep [text](url) links (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description still adds real value beyond them: the default truncation to max_tokens, the content-cleaning rules, link absolutization, and the presence of a token estimate. It omits auth requirements, rate limits, and failure behavior, which keeps it at 4.

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 the primary action and output shape, then a single comparative rationale. Every clause carries information; nothing is redundant with the title or annotations.

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?

With no output schema, the description correctly carries the return shape (Markdown body, title, final URL, token count) and truncation behavior. For an open-world network tool it could still say something about failures, redirect behavior beyond final URL, or rate limits, so it falls slightly short of complete.

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

Parameters4/5

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

Schema coverage is 67%, with max_tokens and include_links already documented in the schema. The description adds meaning to the undocumented url parameter by constraining it to "public URL", and reinforces that output is truncated to max_tokens. It does not explain include_links itself, relying on the schema.

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 and resource ("Fetch a public URL"), states exactly what is returned (main content as clean Markdown plus title, final URL, token count), and makes the transformation explicit (nav/scripts/footers removed, links absolutized). This is clearly distinguishable from reachability checks like check_url or check_robots without needing those siblings named.

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?

"Fetch a public URL" and "Cheaper on context than raw HTML" give clear situational guidance: use this when you want readable page content rather than an HTML dump, and only for public pages. There are no explicit exclusions or error/auth caveats, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources