Skip to main content
Glama

add_class_attendee

Add an attendee to a class in the approved business. If the group does not fit, join the waitlist. Sends a booking or waitlist notice.

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": {
      "sessionId": "<sessionId>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "add_class_attendee"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailYes
phoneNo
spotsNo
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true; the description goes beyond them by disclosing the automatic waitlist fallback and the outbound booking/waitlist notification. It still omits duplicate-registration behavior, permission requirements, and what happens if the session is cancelled or full beyond capacity.

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 core action and its two consequences front-loaded; nothing is redundant. "In the approved business" is slightly vague filler that could be tightened or made concrete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent mutation with five undocumented parameters and no output schema, the description leaves the agent guessing about required inputs, partial-failure behavior, and what the response contains. The waitlist/notification disclosure is useful but not enough to call it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must carry the load and it does not: sessionId, name, email, phone, and especially spots (a 1-20 multi-seat booking) are never explained. The phrase "If the group does not fit" loosely hints at the spots parameter but gives no semantics.

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?

States a specific verb and resource ("Add an attendee to a class") and adds the fallback outcome (waitlist) plus the side effect (sends a booking or waitlist notice). The add/remove pairing with remove_class_attendee is inferable from the verb, though no sibling is named explicitly.

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?

Gives a conditional rule for the full-class case (join the waitlist) but never states when to prefer this over alternatives, nor what prerequisites exist (e.g. session must be open for booking, attendee must not already be registered). Usage is implied rather than directed.

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