Skip to main content
Glama

Cancel an item

evuun_change
DestructiveIdempotent

Cancel one item. Needs this person at level 2 for this arrangement (they paid for it) or a claimed account. Refuses when the cancellation fee would exceed max_fee_minor.

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": {
      "arrangement_id": "<arrangement_id>",
      "item_id": "<item_id>",
      "change": "<change>",
      "max_fee_minor": "<max_fee_minor>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "evuun_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYes
item_idYes
max_fee_minorYes
arrangement_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuine context beyond them, namely the authorization requirement and the hard ceiling behavior tied to max_fee_minor. What is still missing is what the cancellation actually does to the item (refund, seat release) and whether it can be undone.

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?

Three short sentences with the action front-loaded, then the prerequisite, then the failure condition — a sensible order with no filler. The phrase "this person at level 2 for this arrangement" is terse enough to be slightly ambiguous about what level 2 refers to.

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 five-parameter destructive mutation with no output schema, the definition covers the key risk (fee cap) and authorization but says nothing about the response or the post-cancellation state. It is adequate to avoid a wrong call, but not complete enough to predict the outcome.

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%, so the description must carry the parameters, and it only explains max_fee_minor (a ceiling on the cancellation fee that triggers refusal when exceeded). arrangement_id, item_id, change, and idempotency_key get no explanation beyond their patterns and the idempotentHint, so compensation for the coverage gap is only partial.

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?

"Cancel one item" states a specific verb and resource, which is more precise than the generic tool name evuun_change and its single-value enum. It does not name a sibling it is distinguished from, so the agent must infer that this is the cancellation path rather than, say, a rebooking path.

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 supplies a real precondition (level 2 on the arrangement or a claimed account) and an explicit refusal condition (fee above max_fee_minor), which tells the agent when the call will fail before it is made. It stops short of naming an alternative for cases where the prerequisites are not met or the fee cap is too low.

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