Skip to main content
Glama
Bookibles MCP Server

Bookibles MCP Server

bookibles_guide

Explains Bookibles screens, sign-in links, and how to work with bookings, services, availability, and customer messages. Call it first to get oriented before other actions.

Instructions

How to work in Bookibles (bookings, services, availability and customer messages): 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": "bookibles_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Bookibles, 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?

No annotations are supplied, so the description must carry the behavioral burden. It discloses the content scope (screens, sign-in link) but not whether the guide is static documentation or state-dependent, whether it has side effects, or whether the sign-in link requires authentication. For a read-only informational tool these omissions are modest but real.

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 short sentences with no filler, and the operational instruction ("Call this first") is front-loaded at the end of a compact block. The clause "its screens and the sign-in link" is slightly loose wording but still earns its place by scoping the content.

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?

For a low-complexity, single optional-parameter guide tool with no output schema, the description covers domain, contents, and invocation order, which is enough for correct use. Only the nature of the returned material (static vs. dynamic, format) is left unstated.

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?

There is one optional parameter at 100% schema coverage, and the schema already explains it as "What you want done in Bookibles, in your words." The description adds no meaning about how the task string shapes the guide's output, so the baseline 3 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 names the resource domain ("Bookibles (bookings, services, availability and customer messages)") and enumerates what the guide covers: screens and the sign-in link. That distinguishes it from the UI-action siblings like bookibles_click/type. It stops short of a crisp verb+resource framing, but an agent can tell this is the orientation/help tool.

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" gives explicit ordering guidance that routes the agent to this tool before the click/type/open siblings. There are no explicit when-not conditions or named alternatives, but for an orientation tool the entry-point instruction is the operative guidance.

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