Skip to main content
Glama

bolster_open

Open Bolster pages in your signed-in Cloud Browser to review contractor pipelines, draft estimates, and schedule jobs.

Instructions

Open a Bolster page in your signed-in Cloud Browser (default https://app.bolsterbuilt.com) to work with review the contractor pipeline, draft estimates and schedule jobs.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.bolsterbuilt.com

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 page opens in a signed-in Cloud Browser and gives the default URL, but it does not describe navigation side effects, return behavior, or what happens if the page is already open.

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?

The definition is a single front-loaded sentence with no wasted preamble. The phrasing 'to work with review' is slightly awkward, but the core action and context are clear.

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 simple one-parameter navigation tool, the description covers the essential action and default target. It remains thin on post-open behavior and return expectations, which matters more because no annotations or output schema are supplied.

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 description coverage is 100%, so the single url parameter is already documented. The description only repeats the default URL and adds no additional meaning about accepted formats or behavior.

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 states a specific verb and resource: opening a Bolster page in the signed-in Cloud Browser. It is clear enough to distinguish from click/read/type siblings, though it does not explicitly contrast itself with bolster_guide or bolster_status.

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?

It gives example use cases such as reviewing the contractor pipeline, drafting estimates, and scheduling jobs. However, it does not state when to use this instead of sibling tools or any exclusions.

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