Skip to main content
Glama

remove_class_attendee

DestructiveIdempotent

Remove a booking from a class roster by booking ID, return eligible payments and notify attendees promoted from the waitlist.

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": {
      "id": "<id>"
    },
    "name": "remove_class_attendee"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is carried structurally; the description adds real context beyond that by disclosing the two side effects an agent would not otherwise know about: eligible payments are returned and waitlisted attendees are notified of promotion. It does not describe failure modes (e.g. removing an already-removed booking) or permission requirements, keeping it out of the top band.

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?

One front-loaded sentence with the action, the key, and the side effects in order of importance; no filler, no repetition of the tool name or annotations.

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 one-parameter destructive tool with a full annotation set and no output schema, the description covers what is needed to invoke it and what consequences to expect. The remaining gap is the return shape of the 'eligible payments' result, which is not covered by an output schema either.

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 description coverage is 0% and the single parameter is only named 'id', so the description is the sole source of disambiguation: 'by booking ID' clarifies that the UUID identifies a booking rather than a class session or contact, which matters given the many ID-based siblings. It stops short of format or validation detail, but the schema pattern already covers format.

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 ('Remove a booking from a class roster') plus the identifier used ('by booking ID'), which is enough for an agent to tell it apart from the sibling add_class_attendee and from session-level tools like cancel_class_session.

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?

The purpose implies the usage context (dropping a specific attendee from an existing roster), but the description never states preconditions, when to prefer this over cancelling the session, or any exclusions. An agent must infer the when-to-use condition from the verb alone.

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