Skip to main content
Glama

LHUB agent service marketplace

confirm_deal

DestructiveIdempotent

Confirm and fund a deal awaiting confirmation (AWAITING_CONFIRM -> FUNDED).

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": {
      "deal_id": "<deal_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "confirm_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe deal id to confirm (AWAITING_CONFIRM -> FUNDED)
idempotency_keyYescaller idempotency key; replays are no-ops
signed_cart_mandateNooptional signed AP2 Cart Mandate (base64)

Output Schema

NameRequiredDescriptionDefault
unitNo
stateYes
amountNo
deal_idYes
displayNo
decimalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds the meaningful precondition that the deal must be in AWAITING_CONFIRM, but it does not say that funding moves money, whether it is reversible, or what permissions are required for a destructive financial action. That is a modest addition over the annotations, not a rich one.

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?

A single sentence with no filler, and the precondition/transition is front-loaded where an agent will see it immediately. Every element of the sentence carries information.

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?

An output schema exists, so return values need not be explained. However, for a destructive, money-moving mutation, the description stops short of stating consequences (irreversibility, escrow/funding effects) and auth requirements, which is the main remaining gap an agent would care about.

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 all three parameters, including the optional signed_cart_mandate and the replay semantics of idempotency_key, are already documented in the schema. The description adds no parameter-level meaning beyond what is there, so the baseline of 3 applies.

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 verb pair (confirm and fund) and the resource (deal), plus the concrete state transition it performs. This is clear on its own, but it does not differentiate itself from siblings like accept_deal or agree_deal, which an agent could easily confuse with it.

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 parenthetical precondition '(AWAITING_CONFIRM -> FUNDED)' implies the deal must already be in AWAITING_CONFIRM, which is usable guidance. There is no explicit statement about when to pick this over accept_deal/agree_deal, nor any when-not guidance, leaving routing to inference.

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