Skip to main content
Glama

offer

Destructive

Binding offer or counter in the listing currency, at most asking +16%, expiring after 24 hours. Approve amount, currency, terms, pricing and max_fee. Counter names offerId/offerHash. A note is not trading authority.

Input Schema

NameRequiredDescriptionDefault
noteNo
amountYes
lot_idNo
saleIdNo
max_feeYes
offerIdNo
pricingYes
currencyNo
offerHashNo
termsHashYes
request_idYes
acceptTermsNo
contactConsentNo
conversation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / $defs / 1 / $anchor
      Added value: +"s1"
    • addedInput schema / properties / lot_id
      Added value: +{
      +  "$ref": "#s1"
      +}
    • changedInput schema / properties / offerId / $ref
      Previous value: -"#/$defs/1"New value: +"#s1"
    • changedInput schema / properties / saleId / $ref
      Previous value: -"#/$defs/1"New value: +"#s1"
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag this as destructive, non-idempotent and open-world, so the description need not restate irreversibility. It does add real value beyond them: offers are binding, expire after 24 hours, are capped at asking +16%, and 'a note is not trading authority' warns that free-text does not commit anything. It still omits what happens at expiry, what max_fee commits the caller to, and the consequences of submitting a counter.

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?

Three dense sentences with no filler, and the most decision-critical facts (binding, currency, +16% cap, 24h expiry) are front-loaded. Minor cost: 'terms' and 'pricing' are referred to casually while the schema requires a structured pricing object and a termsHash, which can read as looser than the actual contract.

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

Completeness3/5

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

For a 14-parameter, destructive, nested-object tool with no output schema, the description is thinner than the complexity warrants: the pricing/terms object shapes, the request_id idempotency key, and the lot_id versus saleId choice are unaddressed. It does cover the binding, expiring and price-cap behavior that an agent most needs before committing, which keeps it above the floor.

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 description coverage is 0%, so the description carries the full burden, and it only partially does so. It names the approved set (amount, currency, terms, pricing, max_fee) and the counter identifiers, which maps to roughly half the 14 parameters, but request_id, lot_id, saleId, conversation_id, acceptTerms and contactConsent are never explained. It also leaves the pricing and termsHash objects' internal structure entirely to the schema.

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?

States a concrete verb and resource: place a binding offer or counter in the listing currency, and names the fields to approve (amount, currency, terms, pricing, max_fee). It also distinguishes the counter path ('Counter names offerId/offerHash'), so an agent can tell the two modes apart, though it never positions itself against siblings like trade or respond.

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

Usage Guidelines3/5

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

Gives an in-tool condition for choosing the counter mode (supply offerId/offerHash) versus the base mode, plus the hard pricing constraint 'at most asking +16%'. It offers no when-not guidance and no comparison to alternative tools such as trade or respond, so the agent must infer which tool is right.

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