Skip to main content
Glama

Vigil Website MCP

read_page

Read-onlyIdempotent

Read one https://blvigil.com page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: the 40,000-character cap, the Markdown-for-Agents rendering, and a fallback stripped-text mode. The gap is that with only a url parameter, it never says how the Markdown-vs-text choice is made or what happens past the 40,000-character limit.

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?

A single sentence with the action, domain restriction, output modes and size limit front-loaded in that order. No filler and nothing redundant.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the description covers format and size reasonably well. It is still incomplete on the two things an agent would most need: how to select Markdown versus text, and whether exceeding 40,000 characters truncates silently or errors.

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 0% and the single parameter is only typed as a generic URI, so the description must carry the meaning. It does add one real constraint — the page must be on https://blvigil.com — but says nothing about query strings, fragments, or behavior for out-of-domain URLs.

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 (Read) and resource (one https://blvigil.com page) plus the output form (Markdown or stripped text) and a size cap. This clearly separates it from search_pages, though the description never explicitly names that sibling or any other.

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 implied by the singular 'one page' and the fixed domain, so an agent can infer this is for fetching a known URL rather than discovering pages. However, there is no explicit when-to-use statement, no exclusion, and no pointer to search_pages for discovery.

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