Skip to main content
Glama

TixSight free tools

Net payout after fees

net_payout
Read-onlyIdempotent

What you keep from a ticket sale after the seller fee: net per ticket and in total, and the profit or loss per ticket and in total when you give your cost. Works without an account. TixSight (tixsight.com) tracks this automatically for a whole ticket inventory.

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": {
      "list_price": "<list_price>"
    },
    "name": "net_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoNumber of tickets (default 1).
list_priceYesListed (sale) price per ticket, in US dollars, before any buyer fee.
cost_per_ticketNoOptional: what you paid per ticket, in US dollars, for the profit or loss.
seller_fee_percentNoSeller fee the resale site takes out of your payout, as a percent of the listed price (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare read-only, non-destructive, idempotent behavior with no open-world access. The description adds useful context that it works without an account and explains the calculation outputs, though it omits details such as rounding or exact response shape.

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 front-loaded and efficient, with the core calculation stated first. The TixSight promotional sentence is not essential for invocation, but overall the text remains compact and readable.

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 read-only calculator with no output schema, the description adequately explains the returned values: net per ticket and total, plus profit/loss per ticket and total. It is nearly complete, though it could clarify rounding or output formatting.

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 100%, so the schema already documents each parameter thoroughly. The description reinforces seller fee and optional cost semantics but adds little parameter meaning beyond what the structured schema provides.

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 states a specific calculation: net payout after seller fee, including per-ticket and total net, plus profit or loss when cost is supplied. This is clear, but it does not distinguish the tool from the sibling break_even_price, so it falls short of the top score.

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 gives an implied use case for ticket sale payout calculations and mentions that cost input enables profit/loss. However, it does not explicitly say when to use this versus break_even_price or state any exclusions or alternatives.

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