Skip to main content
Glama
Sign In

Surfing Dog Inbox

by ai.surfingdog
OverviewDiscussionsAdmin

Decline what the business proposed

decline_offer
DestructiveIdempotent

Say no to another time or to changes the business proposed (the booking request or the order is closed) or to its quote. To a change it asks for to a confirmed booking or an accepted order, no keeps what was agreed; on a change your person asked for (requested_change), it takes that back. Add reason (and reason_code) for anything your person wants the business to know.

Input Schema

NameRequiredDescriptionDefault
keyNoThe person's key (sdkey1_…), if that is all you have: it is exchanged once for a pass, which comes back in identity.passes — keep the pass and send it next time instead. Never stored.
passNoThe person's passes (sdpass1_…), space-separated, at most 8: presented to the network that issued each, so the business recognises the customer. Or send them in the Sdi-Pass header. Never stored.
reasonNoAnything your person wants the business to know.
item_idYes
offer_idNoThe offer you answer: offer.id from get_item_status. If the business has replaced it since, nothing is done (409 offer_changed, with the current one).
reason_codeNoWhy: price_sensitivity, timing_deferred, quantity, delivery, returns_policy or other.
access_tokenNoCapability secret returned when the item was created without an account.
idempotency_keyNoSame key + same request = same answer. Required for agents. Make it a fresh random UUID per request: a retry of a create with a random key gets its access token again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Same key + same request = same answer. Required for agents."New value: +"Same key + same request = same answer. Required for agents. Make it a fresh random UUID per request: a retry of a create with a random key gets its access token again."
  2. Changed2 schema fields changed
    • addedInput schema / properties / offer_id
      Added value: +{
+  "description": "The offer you answer: offer.id from get_item_status. If the business has replaced it since, nothing is done (409 offer_changed, with the current one).",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / reason_code
      Added value: +{
+  "description": "Why: price_sensitivity, timing_deferred, quantity, delivery, returns_policy or other.",
+  "enum": [
+    "price_sensitivity",
+    "timing_deferred",
+    "quantity",
+    "delivery",
+    "returns_policy",
+    "other"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds semantic consequences: the booking request or order is closed, an agreed change is kept, or a requested change is taken back. It does not elaborate on irreversibility or auth flows, but the schema covers identity and idempotency.

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?

The description is front-loaded with the core action and stays relatively compact. The middle sentence is dense and awkwardly phrased ('To a change it asks for...'), but it carries important semantic distinctions rather than waste.

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?

For an 8-parameter mutation tool with rich schema coverage and annotations, the description covers the key business scenarios and the optional reason fields. Auth, idempotency, and parameter details are handled by the schema, so no major gap remains.

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 88%, so the schema already explains most parameters in detail. The description only calls out reason and reason_code, adding little beyond the schema's own documentation, so baseline 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?

The description uses a clear verb phrase ('Say no to...') and names the resources involved: proposed times, proposed changes, quotes, and requested changes. It is understandable and distinct from accept_offer, though it could more directly label the operation as declining an offer.

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?

It gives concrete usage contexts: declining another time, business-proposed changes, quotes, or taking back a requested_change. It does not explicitly name alternatives such as accept_offer or withdraw_from_contract, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Surfing Dog Inbox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources