Skip to main content
Glama

Respond to an Offer

respond_to_offer
DestructiveIdempotent

Tell us whether an Offer fits what the person asked for. This does not buy, reserve or pay.

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": {
      "request_id": "<request_id>",
      "offer_id": "<offer_id>",
      "verdict": "<verdict>"
    },
    "name": "respond_to_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional short private note for the person. Never include payment details.
verdictYesfits: this Offer matches what the person asked for. does_not_fit: it doesn’t, and it stops counting for them.
offer_idYesThe Offer’s id from get_offers.
request_idYesThe Request’s id from list_requests.
reason_codeNoOptional main reason for does_not_fit.
request_keyNoOptional. The same key repeats a change safely; one is derived when left out.
expected_offer_versionNoThe Offer version you last read.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context — that accepting a verdict does not transact commerce — which annotations alone don't convey. However, annotations flag this as destructive, and the description never discloses that a does_not_fit verdict removes the offer from consideration, leaving the most consequential behavior to the schema.

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?

Two short sentences with zero filler. The action is front-loaded and the scope limitation follows immediately, making it easy to parse at a glance.

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?

An output schema exists and parameter coverage is complete, so the description doesn't need to explain returns or fields. The only meaningful gap is the undisclosed consequence of a does_not_fit verdict, which the definition should have surfaced given the destructive annotation.

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 100%, so every parameter, including the verdict and reason_code enums, is already documented in the schema. The description adds no parameter-level meaning beyond that baseline, so a 3 is appropriate.

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?

Names a specific action (respond with a verdict on an Offer) against a Request, which is distinguishable from sibling tools like get_offers or update_request. It does not explicitly contrast itself with siblings, so it falls short of a 5.

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?

The negative scope statement ("This does not buy, reserve or pay") tells the agent what this is not, but there is no explicit guidance on when to call this versus close_request or update_request. Usage is implied by the name and schema references rather than stated.

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