Skip to main content
Glama

bolster_click

Click a numbered element on the current Bolster page using the element number from the last read to navigate or interact with estimates, proposals, schedules, budgets, or payment requests.

Instructions

Click a numbered element on the current Bolster 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": {
      "element": "<element>"
    },
    "name": "bolster_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/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 of behavioral disclosure. It does not say what clicking does to page state (navigation, form submission, whether the numbering resets), whether the action is reversible, or whether any return value is produced — significant gaps for an interaction tool.

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 or redundancy. Its brevity is efficient, though it leaves no room for the behavioral context an agent needs.

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?

The tool is structurally simple (one integer parameter, no output schema, no annotations), so the description is not badly undersized. Still, an agent gets no information about what happens after the click or how the element numbering is maintained, which are the parts that matter for correct invocation.

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 single parameter already documents itself as "Element number from the last read" with a minimum of 1. The description's word "numbered" adds only marginal reinforcement, so the schema is doing the substantive work.

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?

"Click a numbered element on the current Bolster page" gives a concrete verb (click) and a concrete resource (a numbered element on the current page), which inherently separates it from siblings like bolster_type and bolster_read. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiating.

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?

There is no explicit statement of when to use this instead of bolster_type or bolster_open. The phrase "numbered element" implies the prerequisite workflow (read first, then click that index), but the agent must infer that ordering rather than being told.

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