Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

bookipi_status

Checks whether your Cotlet.dev account, credits, and Bookipi connection are ready before using Bookipi tools.

Instructions

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden, and it discloses very little. It does not state whether the check is read-only and side-effect free, whether it consumes credits, how long it takes, or what a result looks like. For a diagnostic tool the outcome shape (per-check pass/fail versus a single boolean) is the most important behavioral fact, and it is absent.

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 sentence with the object of the check front-loaded and the three checked items enumerated compactly. The colon-list construction is slightly loose ('account' appears both as the owner and as a checked item), but no sentence is wasted.

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?

The tool is simple — no parameters, no nested objects — but there is no output schema, so the description should compensate by indicating what the check reports. It names the three dimensions checked but not the form of the response or what an agent should do when one dimension fails, leaving a real gap for the caller.

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 and the baseline is 4. The description correctly implies no inputs are required by framing the tool as a passive readiness check.

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 uses a specific verb ('Check') and names the resource being assessed: Cotlet.dev account, credits, and the Bookipi connection. It is clearly a readiness/preflight diagnostic rather than an action tool, which distinguishes it from the action siblings (open, click, type, read). It stops short of 5 because 'ready' is never defined — no statement of what a healthy versus unhealthy state means.

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?

Usage is only implied: an agent can infer this is a preflight check to run before attempting Bookipi actions, but the description never says so explicitly and names no alternatives or when-not conditions. With siblings like bookipi_open and bookipi_guide present, one sentence such as 'call this before bookipi_open if you are unsure the connection is live' would have resolved the choice for the agent.

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