BCD — Bridge Control Delegate

read_url

Read-only

Read a public web page or HTTP(S) URL: HTML comes back as readable text, JSON/XML/text as is. offset/length select lines. Sends no cookies or credentials and reads at most 1 MB. Refuses private and local network addresses; a device with a public IPv6 address counts as public.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`length`	No
`offset`	No
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`maxBytes`	No
`timeoutMs`	No
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / workSessionId

Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 30, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations (readOnly/openWorld/non-destructive), the description discloses meaningful behavioral traits: no cookies or credentials are sent, a 1 MB read cap, refusal of private/local addresses, and the IPv6-public caveat. This is exactly the extra context an agent needs and cannot get from the schema or 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?

A single dense paragraph that is front-loaded with the core purpose and then the constraints, with zero filler sentences. Every clause (format handling, offset/length, security posture, size cap, network restriction) earns its place.

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 and 7 parameters, the description does strong work explaining format conversion and safety behavior, but it doesn't describe the shape of the returned content (e.g., line numbering or truncation signaling) that an agent would need to consume results correctly.

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 coverage is only 29%, so the description has to compensate, and it partially does: it explains offset/length ('select lines') and the read-size cap. However deviceId, timeoutMs, workSessionId, and the exact semantics of maxBytes are left to the schema, so the low coverage is not fully offset.

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 states a precise verb+resource ('Read a public web page or HTTP(S) URL') and even specifies the transformation semantics (HTML to text, JSON/XML/text as-is). It clearly conveys what the tool does, but never names a sibling (e.g., read_file, browser_open, browser_snapshot) to disambiguate within the crowded read/browser toolset.

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 through constraints ('public', 'Refuses private and local network addresses') rather than stated as when-to-use guidance. It never says when to prefer this over read_file or the browser_* tools, and gives no exclusions beyond the network-address restriction.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?