Skip to main content
Glama

Add a weekly class

add_weekly_class

Adds a repeating class to the weekly timetable. Classes for the coming days appear on the calendar at once. 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>",
      "weekday": "<weekday>",
      "time": "<time>",
      "class_type_id": "<class_type_id>"
    },
    "name": "add_weekly_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesStart time in the venue’s local time, HH:MM (24h).
spotsNoOptional. Defaults to the class type’s spots (1-50).
addressYesThe venue’s address name, the "name" in name.bookare.app.
weekdayYes0 = Monday … 6 = Sunday.
off_peakNoOptional. Marks the class as off-peak.
access_keyYesThe venue’s access key.
class_type_idYes
instructor_idNoOptional. Id of an instructor.
duration_minutesNoOptional, default 60 (15-240).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's job is to add context, which it does: 'Classes for the coming days appear on the calendar at once' discloses that this creates multiple calendar instances as a side effect. It also flags the venue scoping and the address/access-key requirement, which is real behavioral information beyond the annotations.

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 short sentences with the action front-loaded and the side effect placed second where it is most useful. The final sentence about venue/access key is slightly awkward but carries real information and no filler.

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 9-parameter mutation with no output schema, the description covers the action, the immediate calendar side effect and the venue scoping. It omits what happens when a duplicate schedule already exists (relevant given idempotentHint=false) and what the caller gets back on success, leaving meaningful gaps for a write 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 description coverage is 89%, so the schema already explains weekday numbering, HH:MM time, duration bounds and defaults. The description only restates the address/access-key pairing and adds nothing about how class_type_id, instructor_id or spots interact with the recurring schedule, so the 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?

The description uses a specific verb and resource ('Adds a repeating class to the weekly timetable') that clearly separates it from the class-type and venue tools. It does not explicitly name the sibling mutations (update_weekly_class, remove_weekly_class), so the agent must infer the boundary, but the core action is unambiguous.

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 when-to-use guidance and no mention of alternatives such as update_weekly_class for changing an existing recurring class. The only scoping statement ('Acts on one venue, given its address and access key') describes a constraint rather than telling the agent when this tool is the right choice.

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