Skip to main content
Glama

buildbook_open

Opens a BuildBook page in your signed-in Cloud Browser so you can work with draft estimates, review project tasks, and prepare remodeling invoices.

Instructions

Open a BuildBook page in your signed-in Cloud Browser (default https://app.buildbook.co) to work with draft estimates, review project tasks and prepare remodeling invoices.

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": "buildbook_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.buildbook.co

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 behavioral burden. It usefully discloses that the browser session is 'signed-in,' implying existing auth is reused with no login step, but it says nothing about whether navigation replaces the current tab, what happens on failure, or whether it waits for page load before returning.

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 front-loaded sentence with the action and target first, followed by the default and use cases. The trailing list of remodeling tasks is slightly promotional padding, but nothing is confusing or redundant.

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 zero-required-parameter navigation tool with no output schema this is close to adequate, but it omits the two things an agent most needs: whether the call confirms a loaded page and how the opened page relates to the follow-up read/click/type tools.

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's schema already documents its meaning and default. The description only restates the default URL, adding no syntax, validation, or path guidance beyond the schema — the 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?

The description names a specific verb and resource — opening a BuildBook page in the signed-in Cloud Browser — and lists concrete work the page enables (draft estimates, project tasks, invoices). This clearly separates it from action-level siblings like buildbook_click, buildbook_type, or buildbook_read, though it never explicitly states that distinction.

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?

Use cases are implied ('to work with draft estimates, review project tasks and prepare remodeling invoices'), but there is no statement of when this must be called versus alternatives, nor any note that a page must be opened before click/type/read tools can operate. An agent must infer the entry-point role from context.

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