Skip to main content
Glama
Bookibles MCP Server

Bookibles MCP Server

bookibles_status

Check whether your Cotlet.dev account, credits, and Bookibles connection are ready before using booking tools.

Instructions

Check that your Cotlet.dev account and Bookibles are ready: account, credits and Bookibles 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": "bookibles_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 supplied, the description must carry the behavioral burden. It discloses the three things being verified, which gives useful context, but does not state that the call is read-only, whether failures raise errors or return a status, or what the response 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, front-loaded sentence with the verb first and the checked items enumerated after. No filler, though the colon-list phrasing is slightly compressed.

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 simple zero-parameter status tool the description covers what is inspected, but with no output schema it leaves the return shape (booleans? text? error on failure?) undefined, which an agent needs in order to interpret the result.

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 schema to document and no semantic gap for the description to fill. Baseline of 4 applies.

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 enumerates exactly what is verified: account readiness, credits, and the Bookibles connection. It is clearly a diagnostic/status tool, distinct in kind from the action-oriented siblings (click, open, read, type), though it never names a sibling explicitly.

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 phrasing 'Check that ... are ready' implies a pre-flight or troubleshooting use, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of what to do if the check fails.

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