FullClass

Get one event

get_event

Read-onlyIdempotent

One event in full, by the event_id that list_upcoming_events or list_underfilled_events returned: start and end time, status, instructor, location, price per seat, capacity, seats booked, seats remaining, and seats held right now by customers partway through checkout. Use it for a question about one specific class; for many events at once, use the listing tools.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	the event's id, as returned by list_upcoming_events

Output Schema

Name	Required	Description
`title`	Yes	the event's own name, or the class name when it has no override
`booked`	Yes	seats sold
`status`	Yes	scheduled, canceled, or completed
`ends_at`	Yes
`capacity`	Yes
`currency`	Yes
`event_id`	Yes
`location`	No
`timezone`	Yes
`starts_at`	Yes
`class_name`	Yes
`instructor`	No
`is_private`	Yes
`fill_percent`	Yes
`booking_paused`	Yes	true when the studio has paused new bookings; the event still runs and existing bookings stand
`seats_remaining`	Yes
`seats_in_checkout`	Yes	seats held right now by customers partway through checkout
`price_per_seat_cents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world, non-destructive profile, so the description's added value is the disclosure that the payload is live - 'seats held right now by customers partway through checkout' signals real-time state that a cached-style read might not provide. It does not say how an unknown or stale event_id is handled, which is the one remaining behavioral gap.

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?

Front-loaded with purpose and the ID source, then routing guidance, with zero filler sentences. The long middle clause enumerating return fields is partly redundant with the existing output schema but is at least consolidated in one readable sentence.

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

Completeness5/5

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

For a single-parameter, read-only tool with full schema coverage and an output schema that documents the return shape, the description covers purpose, input provenance, and sibling routing - nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description adds provenance beyond the schema: it notes the id can come from list_underfilled_events as well as list_upcoming_events, while the schema mentions only the latter. That is a real, if small, semantic addition.

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 ('One event in full, by the event_id') and enumerates exactly what comes back, so an agent can distinguish it from the list_* siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('a question about one specific class') and an explicit alternative for the opposite case ('for many events at once, use the listing tools'), naming the sibling family rather than leaving it to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FullClass tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?