Skip to main content
Glama

bolster_status

Check that your Cotlet.dev account, credits, and Bolster connection are ready before managing estimates, proposals, schedules, budgets, and payment requests.

Instructions

Check that your Cotlet.dev account and Bolster are ready: account, credits and Bolster connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. "Check" implies a read-only, non-mutating call, which is useful, but nothing is said about failure reporting, whether it errors or returns a status object, or whether it has side effects like triggering auth.

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?

A single front-loaded sentence with no filler; the three checked items are listed compactly. Slightly awkward phrasing ("your Cotlet.dev account and Bolster are ready") costs it the top score.

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-parameter diagnostic, knowing which three things are verified is the essential information and it is present. However, with no output schema, the description does not indicate what a status result looks like or how a failed check surfaces, leaving a real gap.

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?

The tool takes zero parameters and the description correctly adds no parameter guidance. Baseline 4 applies since there is nothing for the description to clarify beyond the empty schema.

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?

"Check that your Cotlet.dev account and Bolster are ready" names a specific verb (check) and enumerates the resources verified: account, credits, and Bolster connection. This clearly separates it from the action siblings (bolster_click, bolster_open, bolster_type), though the split is inferred from names rather than stated.

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?

The readiness framing implies a pre-flight or troubleshooting check, but the description never says when to call it versus the other bolster_* tools or what to do with a negative result. Usage is only implied, not stated.

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