Skip to main content
Glama

update_class_session

DestructiveIdempotent

Edit one class in the approved business. Supply the full session details. Times are Unix milliseconds. Moving a class notifies attendees.

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>",
      "session": "<session>"
    },
    "name": "update_class_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / session / properties / repeat / properties / count / maximum
      Previous value: -26New value: +52
    • addedInput schema / properties / session / properties / repeat / properties / open
      Added value: +{
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag this as destructive, idempotent, and open-world, so the safety profile is covered. The description adds real value beyond them: it discloses that the whole session must be supplied (overwrite behavior) and that rescheduling notifies attendees — a side effect not visible in the annotations. It stops short of saying what is lost or what permissions are needed.

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?

Four short sentences, each carrying a distinct fact: the action, the full-detail requirement, the timestamp unit, and the attendee-notification consequence. Nothing is repeated and the action is front-loaded.

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 destructive mutation with no output schema and a nested object at 0% schema coverage, the definition covers the highest-risk ambiguities (unit format, full replacement, notification side effect). It is still thin on the recurring-schedule object and on whether omitted siblings of the nested fields are cleared, which matters for an overwrite operation.

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 0%, so the description has to compensate, and it does one important thing: it declares that times are Unix milliseconds, which the integer-typed start/end fields do not convey. However, the nested session fields — repeat cadence/open flag, price default, capacity bounds, assigneeId, locationId — receive no explanation at all.

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?

"Edit one class in the approved business" gives a specific verb (edit), a specific resource (one class), and a scope (single record, approved business). It is clearly distinct from create_class_sessions and cancel_class_session, though it does not name those siblings 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?

"Supply the full session details" implies full-replacement semantics rather than partial patching, which is useful usage guidance, but there is no explicit when-to-use guidance and no statement about when to prefer cancel_class_session or create_class_sessions instead.

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