Skip to main content
Glama

Ready-made setups

list_templates
Read-onlyIdempotent

Typical setups for this kind of venue (classes, timetable and packs; or services; or tables and hours; or units), each with its id and what it adds. 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": "list_templates"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that the call is scoped to a single venue requiring an address and access key, and hints that each entry carries an id plus 'what it adds'. It does not explain ordering, whether the list is a fixed catalog, or how the ids are consumed, and with no output schema those returns stay fuzzy.

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?

Two sentences, front-loaded with the resource definition and the parenthetical enumerating the setup kinds, followed by the venue scoping. Slightly dense but nothing is wasted.

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 simple two-parameter read-only list with no output schema, the description covers what is returned at a high level and the per-venue requirement. It falls short on distinguishing this from other list/get tools and on what the returned ids are for, which matters for an agent deciding to call it.

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 carry their own descriptions, so the schema does the heavy lifting. The description's 'acts on one venue, given its address and access key' reinforces the two-parameter shape but adds no format or validation detail beyond it; baseline 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?

Describes the resource concretely: pre-built venue setups (classes/timetable/packs, services, tables/hours, units) returned with an id and a summary of contents. The verb 'list' comes from the name, and the description does not explicitly differentiate itself from siblings like get_agenda_setup or get_plans, but the content is specific enough to identify the tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives (get_plans, get_agenda_setup, list_units, etc.) or what an agent should do with the returned ids. Only the prerequisite ('acts on one venue, given its address and access key') is implied, leaving usage to be inferred.

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