Skip to main content
Glama

Get Ticket Sale Payout

get_ticket_sale_payout
Read-onlyIdempotent

Find a sale recipient's automatic bank payout ID and dates. Follow nextCursor until matched or null. Requires event_id, ticket_id and recipient_id. Read-only; current event host only.

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": {
      "event_id": "<event_id>",
      "ticket_id": "<ticket_id>",
      "recipient_id": "<recipient_id>"
    },
    "name": "get_ticket_sale_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
event_idYes
ticket_idYes
recipient_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds the authorization scope ('current event host only') and the termination condition for pagination, which the annotations cannot express.

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?

Four short sentences, front-loaded with the outcome, then pagination, prerequisites and scope. Nothing is redundant, though the 'nextCursor'/'cursor' inconsistency is a small structural blemish.

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 4-parameter read with no output schema, the description covers purpose, pagination and permission scope but is thin on what a 'matched' result contains and what happens on no match beyond the implied null. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 parameter meaning. Instead it only restates the required-id list already visible in the schema's required array, and it references 'nextCursor' while the actual parameter is named 'cursor' — a naming mismatch that could confuse the agent about the pagination input.

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?

The description gives a specific verb and resource: 'Find a sale recipient's automatic bank payout ID and dates.' That is concrete enough to separate it from list_ticket_sales or get_event_revenue, though it never names a sibling to contrast against.

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 real usage context: the three required identifiers and the constraint 'current event host only.' Pagination guidance ('Follow nextCursor until matched or null') tells the agent how to iterate, but no alternative tool is named for when a payout record is not the right lookup.

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.