Skip to main content
Glama

Change a weekly class

update_weekly_class

Moves a weekly class to another day or time, or changes its type, instructor, spots, duration or off-peak mark. Only the fields you send change. Dates that already have bookings stay at the old time. 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>",
      "weekly_class_id": "<weekly_class_id>"
    },
    "name": "update_weekly_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoStart 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.
weekdayNo0 = Monday … 6 = Sunday.
off_peakNoOptional. Marks the class as off-peak.
access_keyYesThe venue’s access key.
class_type_idNo
instructor_idNoOptional. Id of an instructor.
weekly_class_idYesId of the weekly class on the timetable.
duration_minutesNoOptional, default 60 (15-240).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses two genuinely non-obvious behaviors: PATCH-style semantics ("Only the fields you send change") and that already-booked dates remain at the old time. It also states the auth/scoping requirement (one venue, by address and access key). It does not say whether invalid field values fail the whole request or what is returned, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the mutation scope, then the partial-update rule, then the booking caveat and auth scoping. No restatement of the title and no filler; every sentence carries information the schema and annotations do not.

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 10-parameter mutation with no output schema, the description covers scope, partial-update semantics, a consequential side effect on booked dates, and the auth/scoping model. The remaining gap is error and response behavior, plus class_type_id having no schema description and only indirect coverage ("changes its type").

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 90%, so the baseline would be 3; the description earns an extra point by clarifying that all non-required fields are optional in effect ("Only the fields you send change"), which is exactly what an agent needs in order to build a partial update. It adds no format or constraint detail beyond the schema, but the schema already carries that.

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?

"Moves a weekly class to another day or time, or changes its type, instructor, spots, duration or off-peak mark" gives a concrete verb (move/change) plus the resource and the exact set of mutable fields. It clearly reads as a modification of an existing timetable entry, which implicitly separates it from add_weekly_class and remove_weekly_class, though no sibling is named.

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?

Usage context is implied rather than stated: the partial-update rule and the venue/access-key scoping tell an agent what it needs to call it, but nothing says when to prefer this over add_weekly_class plus remove_weekly_class, or what preconditions exist (e.g. valid weekly_class_id, authorization to the venue). Adequate minimum, with a clear gap in alternative 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