Skip to main content
Glama

bolster_guide

Explains how to work in Bolster: review the contractor pipeline, draft estimates, and schedule jobs; call first for screens and the sign-in link.

Instructions

How to work in Bolster (review the contractor pipeline, draft estimates and schedule jobs): 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": "bolster_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It implicitly characterizes itself as a passive reference/orientation resource (a guide with screens and a sign-in link), which is useful context, but it never confirms read-only behavior, says whether any session or auth state is required to use the sign-in link, or describes what the returned material looks like. Adequate but thin for an unannotated 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?

Two compact clauses with zero filler, parenthetically enumerating the covered workflows so the agent can pattern-match. The key directive "Call this first" is placed at the end rather than front-loaded, which slightly weakens the structure.

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 low-complexity orientation tool with no output schema and no annotations, the description conveys what topics the guide covers and that it is the starting point. It does not indicate the shape or depth of the returned material (a full screen map? a URL? step-by-step?), leaving the agent unable to anticipate results or know whether a follow-up call is needed.

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 `task` parameter ("What you want done in Bolster, in your words") is already documented in the schema, and one optional parameter puts the baseline at 3. The description adds no detail about how `task` shapes the response, so there is no basis to score above the baseline.

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 resource — a Bolster orientation guide covering the contractor pipeline, estimates, scheduling, screens, and the sign-in link — and prefixes it with a usable framing ("How to work in Bolster"). It distinguishes itself from the action-oriented siblings (click/type/open/read/close) by being the onboarding/reference entry point, though it never says so explicitly.

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?

"Call this first" is an explicit, actionable ordering instruction that tells the agent when to reach for this tool ahead of the sibling automation tools. It stops short of a true when-not clause (e.g., what to do after orientation, or when to skip straight to a UI action), so it falls just short of a 5.

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