Skip to main content
Glama

Set up from a ready-made template

setup_from_template

Fills an empty or new venue with a typical setup in one call: e.g. "pilates" adds class types, a weekly timetable, packs with suggested prices and booking rules. replace_starter = true removes the empty starter class type made at sign-up. Returns what was added. 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>",
      "template_id": "<template_id>"
    },
    "name": "setup_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
template_idYesTemplate id, e.g. pilates, yoga, hair_salon, restaurant, small_hotel, campsite.
replace_starterNoDefault true.

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?

Beyond the annotations, the description discloses that this is a multi-entity bulk write, that replace_starter deletes the sign-up starter class type (a destructive side effect worth flagging given destructiveHint=false), and that it returns what was added. It stops short of warning about the non-idempotent behavior declared in annotations — i.e. what happens if run twice on the same venue.

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 core action and its output, then the parameter nuance, then the return value. Mostly earns its space, though the closing sentence about acting on one venue via address and access key largely restates what the required schema fields already make obvious.

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?

Covers preconditions (empty/new venue), scope (one venue, identified by address and access key), the destructive replace_starter side effect, and the return value, with no output schema needed. The main omission is guidance on behavior when the venue is not empty, relevant given non-idempotent annotations.

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 earns above that by explaining the concrete effect of replace_starter (removes the empty starter class type created at sign-up) rather than just restating its default, and by contextualizing template_id with practical examples of setup types.

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 — fills an empty venue with a complete template setup in one call — and concretely enumerates what that bulk operation produces (class types, weekly timetable, packs with prices and booking rules). This clearly distinguishes it from granular siblings like create_class_type, create_pack, and add_weekly_class.

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?

"Fills an empty or new venue" gives a clear precondition that implies the when-to-use context: initial setup rather than incremental edits. It does not explicitly name the granular alternatives it replaces or state what to do on an already-populated venue, so guidance is clear but not exhaustive.

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