Skip to main content
Glama

TixSight free tools

Break-even listing price

break_even_price
Read-onlyIdempotent

The listing price per ticket needed to break even on resale tickets after the seller fee, with the net per ticket at that price and a one-line explanation. 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": {
      "cost_per_ticket": "<cost_per_ticket>"
    },
    "name": "break_even_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoNumber of tickets (default 1).
extra_costsNoOther costs for the whole order in US dollars, such as delivery (default 0). Spread evenly over the tickets.
cost_per_ticketYesWhat you paid per ticket, in US dollars, including any fees you paid when buying.
buyer_fee_percentNoBuyer fee, as a percent of the listed price (default 0). Buyer fees sit on top of the listed price: the buyer pays them, so they don't change your break-even. The answer shows what the buyer pays.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by sketching the response contents (break-even price, net per ticket, one-line explanation) and by noting that no account is required. The trailing mention that TixSight tracks this automatically is promotional rather than behavioral.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are front-loaded and efficient, defining the output and its components. The final sentence about TixSight tracking a whole inventory is marketing copy that does not help an agent select or invoke the tool, so not every sentence earns its place.

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?

With five well-documented parameters and no output schema, the description covers the essential computation and previews the return values, which is the main gap an absent output schema would otherwise leave. It is slightly thin on how the buyer fee interacts with the returned price, though the schema covers that detail.

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 all five parameters, including the buyer-fee-versus-seller-fee distinction and how extra_costs are spread, are already documented in the schema. The description adds only the framing 'after the seller fee', which is already implied by the schema field. Baseline 3 is appropriate.

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 names a specific output (listing price per ticket needed to break even after the seller fee) plus the accompanying net-per-ticket figure and a one-line explanation. That is a clear verb+resource statement. It does not contrast itself with the sibling net_payout, so the agent must infer which direction of the calculation each tool serves.

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?

There is an implied usage context (pricing resale tickets to break even) and one concrete operational note, 'Works without an account', which helps an unauthenticated agent decide it can call this. However, there is no explicit when-to-use versus when-not, and no mention of the sibling net_payout as the alternative for the reverse calculation.

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