Skip to main content
Glama

Remove a weekly class

remove_weekly_class
Destructive

Takes a class off the weekly timetable. Future dates without bookings disappear; dates that already have bookings stay. 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": "remove_weekly_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
weekly_class_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: deletion is selective — empty future dates vanish while dates with bookings are preserved — which materially changes how an agent should reason about consequences before calling. It stops short of stating whether the class definition itself is retained or how the caller learns which dates survived.

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, front-loaded with the core action before the conditional-deletion nuance. Every sentence carries information, though the trailing venue/address clause is the weakest and partly duplicates the schema's address description.

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 3-parameter destructive mutation with full annotation coverage and no output schema, the definition covers the action, the selective-deletion rule, and the venue scoping — the essentials an agent needs to act. What remains thin is the identifier semantics for weekly_class_id and any note on the outcome after partial deletion.

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 67%; address and access_key are already documented in the schema, so "given its address and access key" mostly restates them, though "Acts on one venue" usefully reinforces the address-as-venue scoping. The undocumented weekly_class_id receives no explanation in the description either, leaving the most important identifier fully undescribed in both places.

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?

"Takes a class off the weekly timetable" states a specific verb (remove) and resource (recurring weekly class) in plain language, and the scoping sentence "Acts on one venue" clarifies the granularity is a single venue's timetable. It doesn't explicitly contrast with update_weekly_class or remove_season, but the destructive framing makes the intent unambiguous.

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?

There is no explicit when-to-use guidance or named alternative (e.g., "use update_weekly_class if you want to change rather than drop the class"). The one implicit routing signal is the note that dates with existing bookings survive, which hints this isn't a full purge, but the agent must infer when this is the right call over update_weekly_class.

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