Skip to main content
Glama

buildbook_status

Checks your Cotlet.dev account, credits, and BuildBook connection to confirm setup is ready before using BuildBook tools.

Instructions

Check that your Cotlet.dev account and BuildBook are ready: account, credits and BuildBook 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": "buildbook_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the full behavioral burden. It does add real substance by naming the three things verified (account, credits, connection), which tells the agent this is a non-mutating diagnostic, but it never states side effects, whether it performs a live network/auth call, or what a failure result looks like.

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 compact sentence with the purpose front-loaded and no filler. The colon-separated list of checked items is efficient, though the phrasing 'your Cotlet.dev account and BuildBook are ready' is slightly tangled with the enumeration that follows.

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?

With no parameters, no annotations, and no output schema, the description is nearly complete for such a simple tool. The remaining gap is that the agent cannot anticipate the shape of the result (per-check pass/fail vs. a single boolean), which matters for deciding next steps after a failed check.

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, so there is nothing for the description to disambiguate; baseline applies. The sentence still usefully frames what the call inspects even though no inputs exist.

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?

States a specific verb ('Check') and enumerates the resources inspected: account, credits, and BuildBook connection. It is clearly a readiness/preflight diagnostic, distinguishable in intent from the action-oriented siblings (open, click, type, read), though it never explicitly names that contrast.

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 phrase 'Check that your ... are ready' implies a preflight use before other BuildBook operations, but there is no explicit guidance on when to call it, whether it should be run before every session, or what to do on failure. Usage must be inferred.

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