Skip to main content
Glama

buildbook_click

Clicks a numbered element on the current BuildBook page. Use the element number from the last read to navigate estimates, schedules, daily logs, bills, or invoices in an agent workflow.

Instructions

Click a numbered element on the current BuildBook 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": "buildbook_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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it says nothing about what a click triggers (navigation, form submission, state change), whether it is reversible, or what happens on an invalid or stale element number. The only behavioral hint is the state dependency implied by 'current BuildBook page'.

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?

One short, front-loaded sentence with no filler or redundant restatement of the tool name. It is efficient, though its brevity borders on under-specification rather than being genuinely tight prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful browser-automation action with no annotations and no output schema, the definition leaves out what the agent most needs: side effects of the click, whether the numbered snapshot is invalidated afterward, and how errors surface. The single parameter is well documented, but the behavioral envelope is not.

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 is documented as 'Element number from the last read,' so the schema does the heavy lifting. The description's 'numbered element' wording is consistent with that but adds no format or boundary detail beyond it; 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?

States a specific verb ('Click') and resource ('a numbered element on the current BuildBook page'), which separates it reasonably from siblings like buildbook_type or buildbook_read. It does not name an alternative explicitly, but the action is unambiguous.

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 only implied: the phrase 'on the current BuildBook page' hints that a page must already be open and elements numbered, presumably from a prior read. There is no explicit when-to-use versus when to prefer buildbook_type or buildbook_read, and no stated preconditions or failure cases.

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