veilbrowser

veil_text

Read a specific element's rendered text using a snapshot reference number, avoiding full page extraction.

Instructions

Read one element's rendered text (innerText) by snapshot ref — a price, status, or result cell — without dumping the whole page.

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": {
      "ref": "<ref>"
    },
    "name": "veil_text"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool is for reading (non-destructive), but lacks details on failure cases, required element visibility, or behavior when ref is invalid. Minimal behavioral disclosure beyond purpose.

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 description is a single, direct sentence with no unnecessary words. It is appropriately sized and front-loads the core action. Could be slightly improved by adding a brief note on return value, but overall concise.

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?

Given no output schema and many sibling tools, the description covers the basic function and use context. However, it lacks parameter details and potential error scenarios, which are important for a tool with only one required parameter. Adequate but not complete.

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?

The only parameter 'ref' is described as a 'snapshot ref' in the description, adding context beyond the schema's type-only definition. However, it does not specify the format or valid range of the ref number, leaving some ambiguity.

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 clearly states the tool reads an element's rendered text by snapshot ref, with examples of use cases (price, status, result cell). It distinguishes itself from dumping the whole page, suggesting a focused read operation. However, it does not explicitly mention the output type despite no output schema.

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?

The phrase 'without dumping the whole page' implies when to use over veil_snapshot, but no explicit when-not-to-use or alternative tools are mentioned. Usage is implied rather than explicitly guided.

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