Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Web Read

web_read
Read-only

Reads the current page of a web session so you can reason over it. mode='text' (visible text, default), 'a11y' (compact accessible tree of links/buttons/fields — best for deciding what to click), or 'html' (raw DOM). Returns an explicit no_session error if the session isn't open, and no_page if it hasn't loaded a page — never a silent empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoWhat to return (default text).
sessionNoSession name (default 'default').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
modeNoThe mode that was read (text/a11y/html).
titleNo
contentNoThe page content in the requested mode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "The page content in the requested mode.",
+      "type": "string"
+    },
+    "mode": {
+      "description": "The mode that was read (text/a11y/html).",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds valuable behavioral detail beyond annotations: it explicitly describes error behavior (no_session, no_page) and guarantees never returning a silent empty result, which helps the agent handle failures correctly. It does not contradict annotations.

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?

The description is two sentences with no waste. The primary purpose is front-loaded, and the mode details and error behavior are packed into a single follow-up sentence that is structured and easy to parse. Every clause earns its place.

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?

For a read-only tool with an output schema defined, the description covers purpose, modes, defaults, and error behavior. It does not need to describe return format because the output schema handles that. It is complete for an agent to call the tool correctly and interpret results.

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 100%, so both parameters are documented. The description adds meaning beyond the schema by explaining the purpose and best use of each mode (e.g., a11y for click decisions) and clarifies the default behavior. This goes beyond the schema's terse 'What to return (default text)'.

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 states a specific verb ('Reads'), a specific resource ('current page of a web session'), and the intent ('so you can reason over it'). It clearly distinguishes from sibling tools like web_navigate, web_click, or web_extract by focusing on reading page content, and the mode list further clarifies scope.

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 gives clear context on when to use the tool (to read page content) and provides mode-specific guidance (e.g., a11y is 'best for deciding what to click'). However, it does not explicitly exclude alternatives or name sibling tools for comparison, leaving some inference to the agent about when to prefer this over web_extract or web_find.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources