Skip to main content
Glama

Bring over check-ins

import_visits

Moving from another system: adds up to 100 past check-ins at once for drop-in class types (no times on the timetable, people just come in), one per member, class type and day. No pack is charged again; the visit is linked to the given pack, or the member’s pack that covered that day. 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>",
      "visits": "<visits>"
    },
    "name": "import_visits"
  }
}

Input Schema

NameRequiredDescriptionDefault
visitsYesUp 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false. The description adds genuinely useful behavior: the 100-row cap, that no pack is charged again, and the pack-resolution fallback ('the visit is linked to the given pack, or the member's pack that covered that day'). It does not address duplicate handling given idempotentHint=false, or what happens when a row fails validation.

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?

Three sentences, front-loaded with the migration context and the hard constraint (drop-in only, max 100). Parentheticals are informative rather than padding, though the last sentence is slightly awkwardly ordered and could lead with the venue scope.

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 only three fully documented parameters and no output schema, the description covers what an agent needs to call it correctly: the cap, the class-type restriction, venue scoping, and pack-charging behavior. Remaining gaps (validation failure semantics, duplicate external_id behavior) are secondary but worth noting given idempotentHint=false.

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: each row is 'one per member, class type and day' (a uniqueness rule the schema does not state) and it explains that address/access_key jointly identify a single venue. That is value beyond the field-level descriptions.

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+resource: adds up to 100 past check-ins in bulk, restricted to drop-in class types, scoped to one venue. The migration framing ('Moving from another system') makes the intent unambiguous. It does not explicitly contrast itself with import_bookings, but the drop-in/no-timetable qualifier does most of the disambiguation work.

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?

The 'Moving from another system' framing and the 'drop-in class types (no times on the timetable)' restriction imply when this tool applies rather than spelling out when-not. No sibling alternative is named, so an agent must infer that timed classes belong to a different import tool.

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