Skip to main content
Glama

Get Ticket Sale Financials

get_ticket_sale_financials
Read-onlyIdempotent

Read a sale's payment references, buyer fees, recipient net proceeds, refunds and affiliate commission. Use event_id and ticket_id from list_ticket_sales. 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>"
    },
    "name": "get_ticket_sale_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
ticket_idYes

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 read-only, idempotent, non-destructive, and closed-world behavior. The description adds a meaningful authorization constraint, 'current event host only', and lists the financial fields exposed, which is useful since no output schema exists.

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 two tight sentences, front-loading the data returned and then the identifier source and permission constraint. Every phrase earns its place with no redundant restatement of the tool name or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read-only getter with no output schema, the description covers the main data fields, the source of identifiers, and the authorization scope. It stops short of describing response formatting or edge cases, but is otherwise complete enough for correct invocation.

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 parameter meaning. It does add provenance by saying both IDs come from list_ticket_sales, but it does not explain what event_id and ticket_id represent beyond being identifiers or how they relate to a sale.

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, 'Read', and enumerates the exact financial data returned: payment references, buyer fees, recipient net proceeds, refunds, and affiliate commission. It clearly identifies the resource as a sale's financials, though it does not explicitly distinguish this tool from the sibling get_ticket_sale_payout.

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?

It tells the agent where to obtain the required identifiers ('Use event_id and ticket_id from list_ticket_sales') and notes the host-only permission scope. However, it gives no guidance on when to use this tool versus related siblings such as get_ticket_sale_payout or get_event_revenue.

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.