Skip to main content
Glama

blueprint_read

Reads the current Blueprint page's text and numbered buttons, links, and fields, optionally limiting output to a specific element.

Instructions

Read the current Blueprint 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": "blueprint_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. Naming the returned content (text, numbered buttons, links, fields) is genuinely useful for a read tool, but it says nothing about whether reads are side-effect free, how large the output can get, or whether the numbering is stable across calls.

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?

A single front-loaded sentence with no filler; the resource comes first and the returned content follows. It could have used the remaining space to state a prerequisite rather than stopping at enumeration.

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?

For a one-optional-param read tool with no output schema, the definition is adequate but not complete: it omits the precondition that a Blueprint page be open and the relationship between the numbered elements it returns and the click/type siblings.

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 100%, so the single optional "element" parameter is already documented as "Read only inside this element." The description adds no scoping or syntax detail beyond that, so the baseline of 3 applies.

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?

"Read the current Blueprint page" pairs a specific verb with a specific resource and enumerates what is returned (text, numbered buttons, links, fields). That distinguishes it from siblings like blueprint_click and blueprint_type, though it never names an alternative directly.

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 "current Blueprint page" implies the page must already be open, and "numbered buttons" hints at how the read output feeds blueprint_click. But there is no explicit when-to-use guidance, no stated prerequisite (e.g., call blueprint_open first), and no exclusion of alternatives.

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