Skip to main content
Glama

Bring over members’ packs

import_member_packs

Moving from another system: adds up to 100 member packs at once, current or past, with their start and expiry dates, classes already used, price and whether (and when) they were paid. No email is sent and no receipt is asked for. Each row refers to a member already imported. Bookings imported later do not take classes again: classes_used is what counts. 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>",
      "packs": "<packs>"
    },
    "name": "import_member_packs"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (write, non-idempotent, not destructive), the description discloses side effects explicitly: no email is sent and no receipt is requested, plus the 100-row batch ceiling and the fact that classes_used includes already-booked future classes and takes precedence over later booking imports. What is not disclosed is what happens on re-runs or partial failures, which matters for a non-idempotent write.

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?

Front-loaded with the situation and the batch limit, then ordered by dependency: rows, side effects, class accounting, venue targeting. Dense but every clause carries information; the field enumeration sentence is the only mildly list-like passage.

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 bulk, non-idempotent migration write with no output schema, the description covers inputs and side effects well but says nothing about outcomes: whether one bad row aborts all 100, whether duplicates are detected via external_id, or what the caller gets back. Those are the questions an agent will have immediately before invoking it.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the per-row referential constraint (member already imported), which fields carry the migrated economic facts (price, paid and paid-on), and the warning not to double-count classes when bookings arrive later. It leaves the member_id vs member_email vs member_external_id selection to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 member packs at once) plus the context that selects it (moving from another system) and the scope (current or past packs, one venue). It also implicitly separates itself from import_bookings by noting bookings imported later do not re-take classes, so an agent can place it in the migration sequence without opening another schema.

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 ordering preconditions: each row refers to a member already imported, and bookings come later because classes_used already accounts for future use. It does not name the non-import alternative for creating packs on sale (create_pack/list_packs), so the exclusion side is inferred rather than stated.

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