Skip to main content
Glama

create_class_sessions

Idempotent

Create one class or a recurring series in the connected business. Times are Unix milliseconds. Reuse the same idempotency key on retry.

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": {
      "session": "<session>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_class_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes
idempotencyKeyYes

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally; the description usefully restates the retry recipe that makes the idempotency hint actionable. It does not disclose side effects of a series creation (how many sessions materialize), whether attendees are notified, or what a partial failure looks like — meaningful gaps for a mutation tool.

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 short sentences, front-loaded with the core action, then the two details most likely to cause a failed call. No filler or redundant restatement of the tool name.

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 two-parameter tool wrapping a deep nested object with zero schema coverage and no output schema, the description covers the two biggest failure modes (epoch units, idempotency) but leaves recurrence semantics and the return value undescribed. Adequate to attempt a correct single-session call; thin for a correct series call.

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?

With 0% schema description coverage the description must compensate, and it does add two high-value facts the schema cannot: timestamps are Unix milliseconds and the idempotency key must be reused on retry. However, the entire nested `session` payload — price, capacity bounds, assigneeId, locationId, and especially the `repeat` object (every/count/open) — carries no semantic explanation anywhere.

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 ('Create one class or a recurring series') and explicitly covers both modes — single session and series — which an agent cannot infer from the schema alone. It doesn't name a sibling to differentiate from (e.g. update_class_session or create_appointment), but the create semantics are 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?

Gives one concrete operational rule ('Reuse the same idempotency key on retry'), which is real when-to guidance, but offers no guidance on when to create a series versus a single class, no prerequisites, and no exclusions relative to siblings like update_class_session or cancel_class_session.

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