Skip to main content
Glama
Bookibles MCP Server

Bookibles MCP Server

bookibles_open

Opens a Bookibles page in your signed-in cloud browser so you can manage bookings, services, availability, and customer messages from an authenticated session.

Instructions

Open a Bookibles page in your signed-in Cloud Browser (default https://bookibles.com/login) to work with bookings, services, availability and customer messages.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://bookibles.com/login

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?

With no annotations, the description carries the full burden. It does disclose a meaningful trait — the browser is already signed in — and gives the default target page, but it omits what happens to any currently open page, whether a new session is created, and what the call returns or how to recover from a failed load.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: the action and target come first, the default URL follows, and the business purpose closes it. No filler or redundancy that doesn't map to a need.

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 one-optional-parameter entry tool with no output schema, the definition covers what to open and where, which is nearly all an agent needs. The only gap is what the call yields after the page loads, which matters for chaining into the read/click/type siblings.

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?

Schema coverage is 100% and the single parameter already documents its default URL, so the description's repetition of the same default adds no new meaning. Baseline 3 applies when the schema does the work.

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 and resource: "Open a Bookibles page in your signed-in Cloud Browser," and names the business domain it enables (bookings, services, availability, messages). It is clearly distinct from sibling verbs like click, type, read and close, though it does not explicitly contrast itself with them.

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 via the trailing purpose clause about working with bookings and services; there is no explicit when-to-use statement, no ordering guidance (e.g., call this before bookibles_click or bookibles_read), and no mention of when bookibles_status might be preferable.

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