Skip to main content
Glama

Buy Listing at the Ask

buy_listing_now
Destructive

Buys a fan listing on XP outright at the seller's asking price, without an offer -- 'buy it now', 'take it at the ask'. Only listings with an asking price can be bought this way, and the purchase is refused if the ask changed since the preview. confirm=false returns a preview of the total; confirm=true completes the sale at once, paid from the caller's XP USDC balance, and commits the seller. The x402 rail is for buy_tickets and does not apply here. identifier comes from list_open_listings or get_open_listing. Requires sign-in.

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": {
      "identifier": "<identifier>"
    },
    "name": "buy_listing_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
railNoHow to pay. 'usdc' spends the caller's XP USDC balance.usdc
confirmNoFalse (default) previews. True buys at ask_per_ticket_usd, the price the preview showed.
identifierYesListing identifier from list_open_listings or get_open_listing.
ask_per_ticket_usdNoThe per-ticket price the preview showed (its ask_per_ticket_usd). Required with confirm=true: the purchase is refused if the seller has changed the ask since, so the buyer never pays a price they did not see.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ask_per_ticket_usd
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The per-ticket price the preview showed (its ask_per_ticket_usd). Required with confirm=true: the purchase is refused if the seller has changed the ask since, so the buyer never pays a price they did not see."
      +}
    • changedInput schema / properties / confirm / description
      Previous value: -"False (default) previews. True buys at the seller's ask as it stands at confirm time."New value: +"False (default) previews. True buys at ask_per_ticket_usd, the price the preview showed."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag this as a non-read-only, destructive, closed-world operation, and the description adds material context on top: sign-in is required, funds come from the caller's XP USDC balance, the seller is committed on confirm=true, and the purchase is refused if the ask changed since the preview. That stale-price refusal rule is a behavioral guarantee an agent could not derive from the annotations.

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?

Front-loads the action and its colloquial aliases for matching, then layers constraints, the preview-vs-commit distinction, the rail exclusion, and the identifier source in a single dense paragraph. No sentence is filler; each clause adds a decision-relevant fact.

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

Completeness5/5

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

For a destructive purchase tool with an output schema already present, the description covers everything an agent needs: prerequisites (sign-in, listing must have an ask), the two-phase preview/commit flow, the price-safety guarantee, funding source, and the behavior of a competing rail. Return values need not be described because the output schema handles them.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description adds some value beyond it: it explains that the preview returns a total, that identifier originates from listing-lookup tools, and that confirm switches between preview and immediate purchase. Most of the confirm/ask_per_ticket_usd semantics are already in the schema, so the added value is real but modest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (buys a fan listing at the seller's asking price) and immediately distinguishes the mechanism from offer-based flows with concrete aliases ('buy it now', 'take it at the ask'). It also rules out a sibling's rail ('The x402 rail is for buy_tickets and does not apply here'), so the agent can separate this from buy_tickets and accept_offer without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit applicability condition (only listings with an asking price can be bought this way), names where the identifier comes from (list_open_listings or get_open_listing), and spells out the two-mode workflow: confirm=false for a preview of the total, confirm=true to complete. It also names the alternative rail for a different tool, leaving little to inference.

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