Skip to main content
Glama

buildbook_guide

Call this first to learn how to draft estimates, review project tasks, and prepare remodeling invoices in BuildBook, including its screens and sign-in link.

Instructions

How to work in BuildBook (draft estimates, review project tasks and prepare remodeling invoices): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in BuildBook, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does tell the agent what it will get back in substance (BuildBook screens and the sign-in link), which implies a non-destructive informational read. It stops short of stating whether the call performs navigation or changes state, and offers no detail on the shape of the response beyond those two items.

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?

It is a single tight sentence-plus-imperative with no filler, and the subject (what the guide covers) is front-loaded before the 'Call this first' instruction. The dense parenthetical is information-bearing rather than redundant, though the phrasing is slightly awkward to parse on first read.

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 guide tool with no output schema and no annotations, the description covers what it does, what it returns, and when to call it. The remaining unknown — whether the returned guidance is prose, a screen list, or a link set — is minor given that no structured output contract exists to contradict.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional 'task' parameter is already described as 'What you want done in BuildBook, in your words', so the baseline is 3. The description earns the extra point by supplying concrete example task types (draft estimates, review project tasks, prepare remodeling invoices), which show the agent the intended granularity of that free-text input rather than just restating it.

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 identifies the resource clearly as orientation material for BuildBook, and the parenthetical enumerates the workflows it covers (draft estimates, project tasks, remodeling invoices) plus concrete content (screens, sign-in link). Its role is distinguishable from the action-oriented siblings (buildbook_click, buildbook_type) because it presents itself as guidance rather than an operation. The verb phrase 'How to work in' is softer than a crisp action verb, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing imperative 'Call this first' gives explicit sequencing guidance relative to the sibling tools, which is the key decision an agent needs to make here. It does not spell out a when-not-to-use condition or what to do after calling it, but for a single entry-point guide tool the routing signal is unambiguous.

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