Skip to main content
Glama

void_event_ticket

Destructive

Void an eligible unpaid event ticket using its event ID and ticket code.

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": {
      "eventId": "<eventId>",
      "code": "<code>"
    },
    "name": "void_event_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
eventIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds the meaningful constraint that only unpaid tickets are eligible, but leaves undefined what "eligible" means, whether voiding is reversible, and what happens on failure.

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?

A single front-loaded sentence with no filler; the action, the resource, the eligibility caveat, and the required inputs all appear without redundancy.

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 destructive mutation the annotations carry the risk signal, but the description is thin on the operational detail that matters here: what makes a ticket eligible, whether a voided ticket can be restored, and what the caller gets back. It is minimally viable rather than complete.

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% — the schema only gives UUID formats with no prose. The description compensates partially by mapping the two parameters to their meaning (event ID identifies the event, code is the ticket code), which is genuinely helpful over bare property names.

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?

"Void" is a specific verb applied to a specific resource (event ticket), with the qualifying scope "eligible unpaid" that separates it from sibling operations like check_in_event_ticket. It could still name the sibling alternative, but the action itself is unambiguous.

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

Usage Guidelines3/5

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

The word "eligible unpaid" implies a precondition (tickets must be unpaid to be voidable), which is useful implied usage guidance. However, it never states when to choose this over check_in_event_ticket or other ticket operations, nor what to do when a ticket is ineligible.

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