Skip to main content
Glama

What has been brought over

import_status
Read-onlyIdempotent

For moving a venue from another system. Shows how many members, packs, bookings and check-ins were imported (and how many exist in total). Imports never email anyone, and re-running with the same external_id values does not create duplicates. 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>"
    },
    "name": "import_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description corroborates the single-venue scope. The notes that imports never email anyone and that re-running with the same external_id avoids duplicates describe the import operations rather than this call, so their value here is mainly interpretive context for the counts; nothing is said about response shape, pagination, or how partial imports are reported.

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?

Four short sentences, front-loaded with the scenario and then the payload, with no filler or marketing language. The trailing sentence about address/access_key is largely redundant with the schema and could be trimmed, but nothing obstructs reading.

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?

There is no output schema, yet the description conveys what comes back (per-entity imported counts plus totals), which is the key thing an agent needs to interpret results. Combined with annotations covering safety and scope, only granular formatting details remain unspecified for this low-complexity two-parameter tool.

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?

Schema coverage is 100% and both parameters (address, access_key) are fully documented in the schema. "Acts on one venue, given its address and access key" merely restates them without adding format, sourcing, or permission detail, so the schema baseline of 3 applies.

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?

"Shows how many members, packs, bookings and check-ins were imported (and how many exist in total)" is a concrete verb+resource statement that makes clear this is a read/report tool, not an import trigger. It is implicitly distinguished from the import_* siblings by describing reporting rather than mutation, though no sibling is named explicitly.

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?

"For moving a venue from another system" sets the scenario, which implies checking status after imports, but the description never states when to call this versus running import_members/import_bookings, or whether it should be called before or after an import. Usage is inferable 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