Read live Perchance editor panes as numbered lines to inspect model source or output HTML, with optional offset and limit.
Read a pane (model=main.pjs, output=index.html) from the LIVE editor as 1-indexed numbered lines.
| Name | Required | Description | Default |
|---|---|---|---|
| pane | No | Default output | |
| limit | No | Max lines. Default 2000 | |
| offset | No | First line (1-indexed). Default 1 |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses that the source is the LIVE editor and the return format is 1-indexed numbered lines, but it omits session requirements, error behavior, and confirmation that it is a read-only operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. Every phrase contributes: the action, the source, the pane identifiers, and the output shape.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with full schema coverage and no output schema, the description explains the return format well enough. The absence of annotations means some safety context is left implicit, but an agent can call this correctly with the given information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds meaning by mapping model to main.pjs and output to index.html, clarifying the enum values beyond the schema's terse 'Default output' label.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Read) and resource (a pane from the LIVE editor) and maps the two pane values to their files. It does not distinguish itself from siblings like perch_outline or perch_grep, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no alternatives named, and no exclusions. The description never explains when this tool is preferable to perch_outline, perch_grep, or perch_pull.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.