Skip to main content
Glama

bolster_read

Reads the current Bolster page's text and numbered interactive elements, optionally scoped to one element, so you can inspect estimates, proposals, schedules, budgets, bids, or payment requests.

Instructions

Read the current Bolster 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": "bolster_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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; "Read" communicates a non-mutating operation but it never states that the page is left unchanged or that this is a snapshot. The phrase "numbered buttons" is a genuinely useful behavioral cue, hinting that element indices are how other tools address elements, but it is left implicit rather than connected to bolst_click.

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 front-loaded sentence with no filler; the verb and scope come first and the return content is enumerated compactly. Nothing here would be cut.

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?

For a one-optional-parameter read tool with no output schema, the description does the essential job of naming the returned content categories. It is slightly thin on prerequisites (open page) and on how the numbered elements map to subsequent click calls, but nothing critical is missing.

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% and the sole parameter already has its own description ("Read only inside this element"), so the schema does the explanatory work. The description never mentions the element parameter or what happens when it is omitted (presumably whole page) — baseline 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 Bolster page" gives a specific verb plus resource, and the elaboration (text, numbered buttons, links, fields) tells an agent exactly what it gets back. It does not explicitly distinguish itself from bolster_status, which could plausibly also report page state, so it stops short of full sibling differentiation.

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 by "current page" — the agent infers a page must already be open via bolster_open before reading. There is no explicit when-to-use/when-not statement and no mention of bolster_status as an alternative for state checks, leaving the choice to inference.

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