aimharder-mcp

Overview Schema Source Related Servers Discussions Admin

prepare_booking_cancellation

Read-only

Prepare cancellation of one exact booked class in a confirmed gym time zone by reading the fresh daily schedule and showing a credit-loss preview before any execution.

Instructions

Read the fresh daily schedule and prepare cancellation of one exact own booked class in a user-confirmed gym IANA zone. No reservation ID or family selector is accepted. Unsupported or ambiguous targets receive no reference. Show possible credit loss, including the published 9NBC 90-minute rule. Preparation sends no POST. Always show the exact full preview and obtain separate account-holder confirmation before execution with confirmed: true. Booking and publication preference switches do not affect this action.

Input Schema

Name	Required	Description	Default
`date`	Yes
`gymId`	No
`endTime`	Yes
`className`	Yes
`startTime`	Yes

Output Schema

Name	Required	Description	Default
`gym`	Yes
`action`	Yes
`credit`	No
`status`	Yes
`target`	Yes
`notices`	Yes
`expiresAt`	No
`alternatives`	Yes
`currentState`	No
`actionReference`	No
`writeConfirmationRequired`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.3Oct 30, 2026

addedOutput schema / properties / writeConfirmationRequired
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "action",
-  "status",
-  "gym",
-  "target",
-  "alternatives",
-  "notices"
-]New value: +[
+  "writeConfirmationRequired",
+  "action",
+  "status",
+  "gym",
+  "target",
+  "alternatives",
+  "notices"
+]

Addedv0.2.0Sep 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, but the description earns its place by adding what annotations cannot: the fresh-schedule read, the absence of any POST during preparation, the credit-loss disclosure requirement including the 9NBC 90-minute rule, and the mandatory two-step confirmation. None of this contradicts the read-only, non-destructive hints.

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?

The purpose and the no-POST scope are front-loaded, and nearly every sentence adds a distinct constraint. A few clauses are dense and slightly compressed ('9NBC 90-minute rule', 'in a user-confirmed gym IANA zone') but nothing is wasted.

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?

With an output schema present, return values need no explanation, and the safety and confirmation sequence is fully covered. What is missing is operational detail on target matching and failure modes beyond 'receive no reference', which matters given the 0% parameter coverage.

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% across 5 parameters, so the description must compensate. It clarifies identification semantics (exact own booked class by class name and time window, not a reservation ID) and that gymId must be a user-confirmed IANA zone, but it does not describe the date/time formats or what the required className matching tolerates.

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 ('prepare cancellation of one exact own booked class') and immediately scopes it against siblings by noting preparation sends no POST and execution happens separately with confirmed: true. An agent can distinguish it from execute_booking_cancellation and prepare_booking_creation without opening any 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?

Explicit exclusions are given ('No reservation ID or family selector is accepted', 'Unsupported or ambiguous targets receive no reference') plus the precondition flow: show the full preview, obtain separate account-holder confirmation, then execute with confirmed: true. It also rules out irrelevant switches ('Booking and publication preference switches do not affect this action').

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

Deploy Server