Skip to main content
Glama

Accept Offer

accept_offer
Destructive

Accepts one buyer's offer on the caller's own listing on XP -- 'accept the $200 offer on my tickets'. The offer comes from a buyer, not from XP. Accepting is a sale and cannot be undone: the seller then transfers the tickets through XP to that buyer by a deadline XP sets at acceptance, and missing it can cancel the sale and forfeit the payout. The deadline is per sale, not a fixed window; the result carries it, or says XP has not set it yet. confirm=false returns a preview of the offer; confirm=true accepts it, and only that call returns success=true. identifier and offer_uuid come from get_my_listing_status. Requires sign-in and the write:listings scope.

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>",
      "offer_uuid": "<offer_uuid>",
      "confirm": "<confirm>"
    },
    "name": "accept_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesRequired. True to accept the offer; False to preview without accepting.
identifierYesPublic listing identifier from list_my_listings or get_my_listing_status.
offer_uuidYesOffer UUID from get_my_listing_status open_offers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations: it discloses irreversibility, that the transfer deadline is set by XP at acceptance and is per-sale rather than a fixed window, that missing it can cancel the sale and forfeit the payout, and that only the confirm=true call returns success=true. Auth and the write:listings scope requirement are also stated.

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?

Front-loads what the tool does and the irreversibility warning, then moves to deadline, confirm semantics, and prerequisites. It is dense but every sentence carries information; the deadline discussion is slightly repetitive ('per sale, not a fixed window' plus 'result carries it').

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, irreversible transaction with an output schema already documenting return shape, the description covers the risk, the confirm gate, parameter provenance, auth, and scope. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains where identifier and offer_uuid originate (get_my_listing_status) and clarifies that only confirm=true produces a success result, which extends the schema's plain boolean note.

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 with scope: 'Accepts one buyer's offer on the caller's own listing on XP'. The example phrase ('accept the $200 offer on my tickets') and the note that the offer comes from a buyer, not XP, pin down exactly which action this is versus reject_offer or buy_listing_now.

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?

Gives a clear when-to-use framing and an explicit preview-vs-commit path (confirm=false preview, confirm=true accepts), plus provenance for both identifiers. It does not name a sibling for the decline path (e.g., reject_offer), so the alternative routing is left slightly implicit.

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