Skip to main content
Glama

Offer status

offer_status
Read-onlyIdempotent

Check the signed-in buyer's latest offer on a listing made with make_offer. Returns the offer's amount in USD, its status (for example pending, accepted, declined or expired) and expiry, plus agreed_price_usd: the price start_purchase will charge if the seller accepted, otherwise null. Returns offer: null if the buyer has made no offer on this listing. Requires a Port66 session.

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": {
      "id": "<id>"
    },
    "name": "offer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"Listing id (the slug from search_listings)"New value: +"The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure')."
    • addedInput schema / properties / id / minLength
      Added value: +1
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive open-world call, and the description is consistent with that. It adds useful behavior beyond them — the exact fields returned, the null semantics for agreed_price_usd, the empty-state (offer: null), and the session requirement — but says nothing about rate limits, caching, or staleness of the offer status.

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 action, then return values, then the null case, then the auth requirement — a sensible ordering with little waste. The sentence about agreed_price_usd is slightly dense but each clause carries information.

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 no output schema, the description must carry the return contract, and it does: the fields, the status vocabulary examples, the agreed_price_usd conditional, and the no-offer null case. Only minor items such as how stale a 'pending' status can be are left uncovered.

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%, and the single `id` parameter is fully documented in the schema with a slug example. The description only restates that the check is scoped 'on a listing' and adds no format or sourcing detail beyond what the schema already provides, so the baseline 3 applies.

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 ('Check the signed-in buyer's latest offer on a listing') and explicitly ties the object to make_offer, so it's distinguishable from the sibling that creates offers. The scope word 'latest' also prevents misuse as a full offer history.

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 description situates the tool in a workflow by naming make_offer as the producer of the offer being checked and start_purchase as the consumer of agreed_price_usd, which tells the agent when the result becomes actionable. It stops short of explicit when-not guidance or naming other alternatives such as purchase_status for the transaction side.

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