Skip to main content
Glama

FavCRM

by io.favcrm

cancel_booking

Destructive

Cancel a booking and create a durable refund receipt. Uses the merchant refund setting unless refundMethod is provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoCancellation reason
bookingIdYesThe booking ID to cancel
refundMethodNoRefund cash manually or convert refundable cash to member credit
idempotencyKeyYesUnique key for this cancellation attempt; reuse it only when retrying the same request

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

TDQS

A4.1/5.0
Behavior4/5

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

The description adds valuable context beyond the destructiveHint annotation by noting the creation of a durable refund receipt and the default refund behavior. It does not contradict the annotations, and while it could mention idempotency behavior, the schema already details idempotencyKey.

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?

The description is concise, two sentences, and front-loaded with the core action. Every sentence adds meaningful information without redundancy.

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?

Given the presence of a detailed input schema, annotations (destructiveHint, idempotentHint false), and an output schema, the description sufficiently covers the purpose and key behavior. No critical information is missing for an agent to select and invoke this tool.

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. The description enhances parameter understanding by explaining that the merchant refund setting is used unless refundMethod is provided, which clarifies the default behavior for the refundMethod parameter.

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?

The description clearly states the action ('Cancel a booking') and the expected outcome ('create a durable refund receipt'). This distinguishes it from sibling tools like confirm_booking, complete_booking, and mark_no_show by focusing on cancellation with a refund artifact.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives is provided. There is no mention of prerequisites, such as the booking being in a cancellable state, or any exclusion like 'use confirm_booking for confirmed bookings'.

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

All FavCRM toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools have overlapping boundaries, such as generate_post_cover/attach_post_cover_from_job/upload_post_cover_from_url, update_deal/update_deal_stage/mark_deal_won/mark_deal_lost, and booking status transitions (confirm/cancel/complete/mark_no_show). The catch-all execute_tool adds further ambiguity.

Naming Consistency4/5

Nearly all tools follow a consistent verb_noun snake_case convention (create_*, list_*, get_*, update_*, delete_*, restore_*). Minor exceptions like 'clone' and 'execute_tool' are still readable and do not significantly break the pattern.

Tool Count1/5

With 223 tools, the server is extremely over-scoped. Even for a full CRM platform, this many tools overwhelms context windows and makes tool selection impractical. It far exceeds the reasonable range for an MCP server.

Completeness3/5

The surface is broad but has notable gaps: no update_booking/delete_booking, no delete_product, no send_message/send_campaign (referenced but absent), and no delete_staff/resource. Some workflows dead-end or require manual approval steps.

Resources