Skip to main content
Glama

plancraft_read

Read the current Plancraft page text and numbered buttons, links, and fields, optionally limited to one element, so agents can inspect page content before acting.

Instructions

Read the current Plancraft page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plancraft_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of what is returned (text plus numbered buttons, links and fields), which usefully implies the numbering scheme that plancraft_click likely consumes, but it says nothing about read-only/safety guarantees, page size limits, or whether element indices stay stable between reads.

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?

One sentence, front-loaded with the verb and target, and every clause adds information about the payload. Nothing could be removed without losing content.

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?

A simple read tool with one optional parameter and no output schema; the description adequately characterizes the return value. The remaining gap is that the numbering scheme that ties this output to plancraft_click is not spelled out, which matters for a multi-tool browsing loop.

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% and the single parameter is documented in the schema as "Read only inside this element", so baseline 3 applies. The description's mention of numbered elements is consistent with that scoping parameter, giving a slight lift over the schema alone.

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 (the current Plancraft page), then enumerates what comes back: text, numbered buttons, links and fields. That is enough to tell it apart from plancraft_click/plancraft_type, which act on the page rather than dump it, though the description never names those alternatives.

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 word "current" implies a page must already be open via plancraft_open, but the description never states that precondition explicitly, nor when to re-read versus relying on prior output. Usage is implied rather than prescribed; there are no exclusions or alternative routing.

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