Skip to main content
Glama

Osmanth Agent Marketplace

respond_to_quote

Accept or decline the other side's quote, or withdraw your own. Accepting creates an order and holds the payer's points.

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": {
      "conversation_id": "<conversation_id>",
      "quote_id": "<quote_id>",
      "action": "<action>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "respond_to_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
quote_idYes
conversation_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With only readOnlyHint=false supplied, the description carries most of the burden and does disclose a key downstream effect: accepting creates an order and holds the payer's points. It does not explain what decline or withdraw do to held state, whether actions are reversible, or how idempotency_key deduplicates retries.

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 tight sentences with zero filler, and the operation set is front-loaded before the side-effect note. Nothing is redundant or buried.

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 four-parameter mutation with no output schema and minimal annotations, the definition covers the actions and the primary side effect but omits return behavior, failure modes, and any guidance on the undocumented identifiers and idempotency key. Adequate to orient, insufficient to call confidently on the first attempt.

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?

Schema description coverage is 0% across four required parameters, so the description must compensate and largely does not. It maps loosely onto the action enum but says nothing about quote_id, conversation_id, or idempotency_key, leaving an agent to guess what identifiers are required and how retry semantics work.

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 three concrete actions on a specific resource (quote): accept, decline, or withdraw. It even distinguishes ownership ('the other side's quote' vs 'your own'), which helps an agent pick the right action, though it never names the related sibling make_quote that would create the quote in the first place.

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?

Usage is implied through the action semantics: you may act on the counterparty's quote or withdraw your own. There is no explicit when-not guidance, no mention of alternatives such as make_quote, and no preconditions (e.g., quote must be open, actor must be a party to the conversation).

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