Skip to main content
Glama

knowledge-base

by com.tunnelpowered

cancel_order

Cancel an order you placed with commit_order. Returns settled. True means it is cancelled, the business has been told and their day is free again. False comes with a reason: "inside-cancel-window" (later notice than they said they need), "no-cancel-window-set" (they never said), "order-passed", "not-open" (already cancelled or withdrawn) or "not-the-issuing-agent". Every reason but the last two puts the request in front of the business and returns an escalation to poll with check_escalation — a refusal here is a question being asked, not a dead end. Also returns refund, which is the business's OWN published terms at the notice given. tunnel settles no money and holds none: nothing has been paid or refunded, and only the business can act on it. Authentication: bearer token required, and it must be the same agent that placed the order. Anyone else holding the reference gets the request routed to the business instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesThe `ref` returned by commit_order. It is the only handle on this order.
noteNoOptional. Why, in the buyer's own words. Recorded, shown to the business and carried into the question if a person has to decide. Never parsed, and it cannot change the answer.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully discloses the behavioral contract: return values (settled), possible reasons with explanations, escalation behavior, refund semantics, legacy settlement, and authentication requirements. It covers the full lifecycle of a cancellation attempt.

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 description is dense but well-structured, each sentence adding necessary detail about outcomes, reasons, and actions. It is longer than the minimal viable description, but the complexity of the cancellation flow justifies the length 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 tool's complexity and the absence of an output schema, the description fully explains return values, error conditions, and next steps (e.g., polling check_escalation). It also covers edge cases like reauthentication and delegation, making it complete for agent use.

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?

The schema already describes both parameters (ref and note) with 100% coverage, but the description adds essential nuance: ref is the only handle on the order, and note is never parsed and cannot change the outcome. This goes beyond the schema to clarify parameter intent.

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 tool cancels an order placed with commit_order, specifying the action and resource. It distinguishes from sibling tools like request_order_change and reschedule_order by focusing solely on cancellation and detailing the outcome.

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

Usage Guidelines4/5

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

It gives clear context: use this for canceling orders you placed with commit_order, and references check_escalation for polling follow-ups. However, it does not explicitly mention alternatives like request_order_change or state when not to use this tool, leaving some room for interpretation.

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

All knowledge-base 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

A4.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but ask_business and ask_business_freeform both serve the core function of asking a question about a listing, which could cause misselection. The detailed descriptions mitigate the overlap, but the similar intent remains a minor ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (ask_, check_, contact_, get_, search_, send_), with only ask_business_freeform adding a modifier that still fits the convention. Naming is predictable and readable.

Tool Count5/5

Nine tools is well-scoped for a knowledge base server, covering discovery (search, get), questioning (ask), asynchronous communication (contact, followup, replies, escalation), and verification. Each tool earns its place without unnecessary bloat.

Completeness5/5

The tool set provides full coverage of the domain: finding businesses, reading profiles, asking structured and freeform questions, escalating unresolved queries, opening and continuing conversations, and checking verification. Poll-based tools handle dead ends explicitly, so there are no obvious gaps.

Resources