Skip to main content
Glama

mcp.xynaptic

ticket-buy

Xynaptic Ticket — prepaid credit: pay once (0.5-20 USDC), get a ticket_id|ticket_secret, consume any service with header X-TICKET at 20% off. Valid 90 days. POST { amount_usd }. Usage: Use to preload a prepaid ticket at -20% for cost-efficient batches of calls. [price: $0.500 per call, x402/USDC]

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": {
      "body": "<body>"
    },
    "name": "ticket-buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON request body (POST endpoint)
paramsNooptional query parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / body / properties / credit_usdc
      Added value: +{
      +  "description": "example: 0.5",
      +  "type": "number"
      +}
    • addedInput schema / properties / body / properties / expires_at
      Added value: +{
      +  "description": "example: \"2026-12-12T00:00:00Z\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / ticket_id
      Added value: +{
      +  "description": "example: \"tkt_...\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / ticket_secret
      Added value: +{
      +  "description": "example: \"xyn_...\"",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / body / required
      Added value: +[]
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "body"
      +]
  3. Changed4 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)"New value: +"JSON request body (POST endpoint)"
    • addedInput schema / properties / body / properties
      Added value: +{}
    • changedInput schema / properties / params / description
      Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"optional query parameters"
    • addedInput schema / required
      Added value: +[]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the payment rail (x402/USDC), the spend band, the returned credentials, the 90-day validity window, and the per-call price. It does not say whether a purchase is refundable, whether repeat buys stack, or what happens on payment failure — relevant gaps for a paid mutation.

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 core mechanics are front-loaded and the sentences are dense with signal rather than filler. There is mild redundancy between the '20% off' claim and the trailing '[price: $0.500 per call, x402/USDC]' tag, but overall it is appropriately sized.

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 payment-bearing tool with no annotations and no output schema, the description is unusually complete — it explains price, discount, credential issuance, header usage, and expiry, which covers most of what an agent needs before spending money. It is only short of failure/refund semantics and an explicit statement of how the ticket is later presented per service.

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 coverage is 100%, so the baseline is 3, and the description does usefully name the actual request payload as 'POST { amount_usd }'. However, that name conflicts with the schema, whose body properties (ticket_id, expires_at, credit_usdc, ticket_secret) look like response fields rather than inputs, so an agent cannot fully reconcile what to send versus what it will receive.

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 uses a specific verb and resource — buy a prepaid ticket that yields a ticket_id|ticket_secret consumed via the X-TICKET header — and states the economics (0.5–20 USDC, 20% off, 90 days). It is unambiguous about what the tool produces, though it never contrasts itself with the sibling tools (e.g. xynaptic-status or xynaptic-catalog) that presumably inspect the resulting ticket.

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?

The 'Usage' sentence gives a clear positive trigger: preload a ticket at -20% when batching many calls for cost efficiency. It stops short of stating when NOT to buy (e.g. one-off calls, expired tickets, or when a ticket already exists), so an agent must infer the exclusions.

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