Skip to main content
Glama

Bring over members

import_members

Moving from another system: adds up to 100 existing or former members at once, with their join date and status. No email is sent. A row whose external_id was imported before, or whose email already exists here, is reported as existing and left unchanged. Needs email, phone or external_id per row. Members who joined in the last 90 days count towards the plan’s member limit. 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>",
      "members": "<members>"
    },
    "name": "import_members"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations: no email is sent, previously imported external_ids or duplicate emails are reported as existing and left unchanged, and rows joined within 90 days count toward the plan's member limit. These are non-obvious side effects and quota implications an agent could not infer from readOnlyHint=false / destructiveHint=false. It stops short of describing the response payload that would make the 'reported as existing' outcome actionable.

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 and front-loaded: the scenario, then limits, then side effects, then dedup rules, then identity requirement, then quota, then scoping. Nearly every sentence carries unique operational information. Slightly compressed prose with several facts packed per sentence, but no filler.

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 batch mutation tool with no output schema, it covers side effects, dedup, quota impact, and venue scoping well. The remaining gap is what the tool returns — the description alludes to rows being 'reported as existing' but never says whether a per-row result summary comes back, which matters for a partial-success batch operation.

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 baseline is 3, but the description adds real meaning the schema does not: the schema requires only 'name', while the description states each row needs email, phone, or external_id — a per-row constraint that would otherwise cause failed imports. It also surfaces the 100-row cap at the top rather than buried in the array description.

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?

Names a specific verb and resource (adds/imports members), states batch scope (up to 100), and frames the scenario (moving from another system) so the agent can distinguish this from import_bookings, import_visits, and the add_* siblings. The final sentence pins the operation to a single venue identified by address and access key.

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?

The opening clause establishes the condition under which this tool applies (migration from another system) and the dedup rule implicitly tells the agent re-running is safe-ish. It does not name an alternative tool or state when NOT to use it, so the guidance is clear context rather than explicit routing.

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