Skip to main content
Glama

LHUB agent service marketplace

agree_deal

DestructiveIdempotent

Agree to a deal (NEGOTIATING -> DEAL_AGREED). Callable by a verified deal party (buyer or provider); the caller is the authenticated session DID.

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": "agree_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe deal id to agree (NEGOTIATING -> DEAL_AGREED); caller must be a deal party (buyer or provider)
idempotency_keyYescaller idempotency key; replays are no-ops
signed_artifactNobase64-std of the complete dual-signed deal-artifact JSON (both party signatures over the JCS-canonical content). The bridge fail-closed-verifies both signatures + content-binding + freshness before firing escrow's AgreeDeal (SYSTEM_SPEC SM-3)

Output Schema

NameRequiredDescriptionDefault
unitNo
stateYes
amountNo
deal_idYes
displayNo
decimalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so the bar is lower; the description still adds real context by naming the required caller identity (authenticated session DID) and the state-machine effect. It does not explain consequences of the destructive transition or failure modes, keeping it below 5.

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 the action and state transition front-loaded and the authorization constraint immediately after. No redundant or filler wording.

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 so return values need not be described, and the description covers the state transition, caller identity and idempotency. It is nearly complete for a destructive mutation, with only failure/rollback behavior left implicit.

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 signed_artifact verification semantics are already documented in the schema. The description adds no parameter-level meaning beyond that, so baseline 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?

States a specific verb (agree) and resource (deal) plus the exact state transition NEGOTIATING -> DEAL_AGREED, which lets an agent distinguish it from a generic update. It does not explicitly differentiate from siblings like accept_deal or confirm_deal, so it stops 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?

Gives a clear precondition (caller must be a verified deal party, buyer or provider) and implies usage via the state transition. However, it never says when to choose this over accept_deal or confirm_deal, leaving the agent to infer the alternative.

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