Skip to main content
Glama

respond

Destructive

Explicitly accept, decline or withdraw the exact current offerId/offerHash. The decision changes the proposal and can notify its participants. Acceptance binds the agreed amount and currency. Use the proposal’s frozen acceptance pricing and fee.

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>",
      "max_fee": "<max_fee>",
      "pricing": "<pricing>",
      "termsHash": "<termsHash>",
      "offerId": "<offerId>",
      "offerHash": "<offerHash>",
      "response": "<response>"
    },
    "name": "respond"
  }
}

Input Schema

NameRequiredDescriptionDefault
lot_idNo
saleIdNo
max_feeYes
offerIdYes
pricingYes
responseYes
offerHashYes
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
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, and openWorld=true, so the safety profile is covered. The description adds genuinely non-derivable behavior: the decision mutates the proposal, may notify participants, and acceptance binds the agreed amount and currency. It stops short of describing what happens on conflicting or stale offers, which is the main residual risk for a non-idempotent destructive action.

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?

Four short sentences, front-loaded with the action and target, with no filler. The pricing sentence is slightly disconnected from the rest but still earns its place by constraining the fee input.

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?

The tool is complex (12 params, nested objects, 7 required, destructive, no output schema), and the description covers the semantic core and side effects well. It is nevertheless incomplete for calling the tool: most parameters and the semantics of hash/ID fields (termsHash vs offerHash vs pricing.sha256) are undocumented anywhere, which is a real gap at 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 12 parameters and 0% schema description coverage, the description must carry the load. It only glosses offerId, offerHash, pricing/max_fee, and the response enum; request_id, termsHash, saleId, lot_id, acceptTerms, contactConsent, and conversation_id are entirely unexplained, as are the nested pricing/contactConsent object shapes.

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?

The description states a specific verb set (accept, decline, withdraw) applied to a specific resource (the current offerId/offerHash), which clearly separates it from browsing or negotiation siblings like offer or reply. It is clear but does not explicitly name which sibling to use for adjacent actions, keeping it just 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?

There is implied guidance that this applies only to the *exact current* offerId/offerHash and that acceptance pricing must be frozen rather than recomputed. However, it never says when to call respond versus offer, manage_thread, or reply, and gives no prerequisites for obtaining the offerId/offerHash.

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