Skip to main content
Glama

Bring over bookings and class history

import_bookings

Moving from another system: adds up to 100 bookings at once, past (with attendance) or upcoming. Each row names the class by class_id, or by date, time and class_type_id; a past class that is not on the calendar is created. An upcoming class must already be on the calendar. Nothing is emailed and no pack is charged again (classes_used on the imported pack already counts them); the booking is linked to the member’s pack so a later cancellation gives the class back. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "bookings": "<bookings>"
    },
    "name": "import_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
bookingsYesUp to 100 rows.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), and the description adds non-obvious behavior the annotations cannot convey: no emails are sent, no pack is re-charged because classes_used already counts the booking, and the booking is linked to the pack so a later cancellation returns the class. It also discloses the side effect that a past class off the calendar gets created. It does not state what happens on partial failure or how external_id deduplication behaves, which is a notable gap for a non-idempotent batch import.

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?

Dense but purposeful: scenario, batch limit, class-identification rules, side effects and venue scoping each appear once. It is a single run-on paragraph, so the key scoping constraint ('Acts on one venue') lands last instead of being front-loaded.

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 100-row batch import with no output schema, it covers the prerequisites (venue address and access key), row shape alternatives, and the critical no-double-charge behavior. It leaves return/error semantics and deduplication on external_id unexplained, which an agent would reasonably want before retrying a failed import.

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?

The description's main contribution is the rule that a row identifies a class either by class_id or by date, time and class_type_id, plus that instructor_id and duration_minutes apply only when a class is created. With schema coverage at 100%, the per-field meaning is already documented in the schema, so the added semantic value is real but modest. Baseline 3 fits.

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 ('adds up to 100 bookings at once, past ... or upcoming') plus the scenario ('Moving from another system'), so an agent can identify the operation immediately. It does not explicitly contrast itself with sibling import tools such as import_visits or import_member_packs, leaving differentiation to inference.

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?

Gives clear context for when this applies (migrating from another system) and distinguishes the two modes: past classes may be created if absent, upcoming classes must already exist on the calendar. It stops short of naming an alternative tool or stating when not to use this one.

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