Skip to main content
Glama

The public booking page

dosai_get_booking_page
Read-onlyIdempotent

The client booking page (dosai.pro/b/...); when on, the bot also books through it and links to it. On/off, address, services, schedule (schedule_source bot = the bot's calendar function, see bot_schedule; own = the page's), page.resources (who takes bookings, each on a bot schedule), calendar_ok, prepayment, payment_state (no_cashbox = no prepayment, not_ready = prepaid booking stopped), 30-day stats, latest requests.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "dosai_get_booking_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, closed-world read, so the description does not need to restate safety. It does add real behavioral detail beyond the annotations: that when the page is on, the bot books through it and links to it, plus decoded enum meanings for schedule_source and payment_state (no_cashbox, not_ready).

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

Conciseness3/5

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

It is a single densely packed sentence with the URL and the on/off behavior front-loaded, which is good, but the remaining field list reads as a comma dump of variable names rather than a structured overview. Nothing is wasted, yet the scanning cost for an agent is higher than necessary.

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 output schema and only one fully documented parameter, the description must carry the return shape, and it does so thoroughly, including the meaning of ambiguous values. What is missing is guidance on selecting this tool over its nearby read siblings, which matters given the dense sibling set.

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 a single parameter, project_id, and schema description coverage is 100% ('From dosai_list_projects'), so the schema already carries the meaning. The description adds nothing further about the parameter, which is fine at baseline but earns no credit above it.

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 identifies the exact resource (the client booking page at dosai.pro/b/...) and enumerates its contents, so an agent can tell it apart from dosai_update_booking_page or the settings/system getters. It lacks an explicit verb such as 'retrieve', leaving the read intent to be inferred from the title and the enumerated fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus dosai_get_booking_settings, dosai_get_booking_system, or dosai_update_booking_page. The only cross-reference, 'see bot_schedule', explains a field value (schedule_source) rather than directing tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources