Skip to main content
Glama

Respond to a Resollo offer

offers.respond
Destructive

Responds to a pending Make an Offer / bargaining offer. If the caller is the SELLER of the offer, action must be 'accept', 'reject', or 'counter' (counter_price required for 'counter') and the offer must currently be pending. If the caller is the BUYER, action is 'accept_counter' (the offer must currently be countered) or 'withdraw' (the offer must be pending or countered; withdrawing a countered offer declines the counter, and the buyer can't make a new offer on that product for 48 hours). Accepting an offer or a counter-offer immediately creates a confirmed order at the agreed price -- it does NOT charge any payment method, the buyer still completes payment themselves afterwards through the normal flow, exactly like after orders.place. Requires a signed-in Resollo user (OAuth sign-in, or an 'Authorization: Bearer ' header).

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": {
      "offer_id": "<offer_id>",
      "action": "<action>"
    },
    "name": "offers.respond"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesSeller actions on a pending offer: accept | reject | counter (counter_price required). Buyer actions: accept_counter on a countered offer; withdraw on a pending or countered offer (declines a counter). After a withdrawal the buyer can't make a new offer on the same product for 48 hours.
offer_idYesThe uuid of the offer to respond to.
counter_priceNoThe seller's counter-offer price. Required when action is `counter`.

Output Schema

NameRequiredDescriptionDefault
stateYes
offer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Seller actions on a pending offer: accept | reject | counter (counter_price required). Buyer action on a countered offer: accept_counter."New value: +"Seller actions on a pending offer: accept | reject | counter (counter_price required). Buyer actions: accept_counter on a countered offer; withdraw on a pending or countered offer (declines a counter). After a withdrawal the buyer can't make a new offer on the same product for 48 hours."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "accept",
      -  "reject",
      -  "counter",
      -  "accept_counter"
      -]New value: +[
      +  "accept",
      +  "reject",
      +  "counter",
      +  "accept_counter",
      +  "withdraw"
      +]
    • changedOutput schema / properties / state / enum
      Previous value: -[
      -  "accepted",
      -  "rejected",
      -  "countered",
      -  "buyer_accepted"
      -]New value: +[
      +  "accepted",
      +  "rejected",
      +  "countered",
      +  "buyer_accepted",
      +  "withdrawn"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnly=false, but the description goes well beyond them: it discloses that accepting creates a confirmed order immediately without charging any payment method, that the buyer completes payment afterward, and that withdrawal imposes a 48-hour cooldown. That is meaningful side-effect disclosure an agent could not infer from annotations. It stops short of describing response payload or error behavior, hence a 4 rather than 5.

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-loaded with the core verb and resource, then organized by role, which is the right structure for a multi-action tool. The payment paragraph is long but every clause earns its place; only minor tightening would help.

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?

Covers auth requirements (signed-in user, OAuth or Bearer agent key), state preconditions per action, side effects, and the payment handoff analogy to orders.place. An output schema exists, so the absence of return-value prose is not a gap.

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?

With 100% schema coverage the baseline is 3, and the description adds role-conditioned meaning about which action values are legal under which offer state rather than merely restating the enum. It does repeat much of what the schema's action description already says (48-hour cooldown, counter_price requirement), so the incremental value is modest but real.

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 ("Responds to a pending Make an Offer / bargaining offer") and immediately splits the behavior by caller role (SELLER vs BUYER), which is the key distinguishing axis. An agent can tell exactly what this does and which actions apply to it.

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?

Enumerates precisely which action values are valid for which role and what state the offer must be in (pending vs countered) for each. It also gives the exclusion case implicitly — the buyer cannot accept a pending offer, only accept_counter on a countered one — and explains consequences (48-hour new-offer lockout after withdrawal, counter declined on withdraw).

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