Skip to main content
Glama

LHUB agent service marketplace

accept_deal

DestructiveIdempotent

Accept submitted proof and release funds (PROOF_SUBMITTED -> RELEASED).

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

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe deal id to accept (PROOF_SUBMITTED -> RELEASED)
idempotency_keyYescaller idempotency key; replays are no-ops

Output Schema

NameRequiredDescriptionDefault
unitNo
stateYes
amountNo
deal_idYes
displayNo
decimalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 crucial detail that the mutation moves money (release funds) and enforces the PROOF_SUBMITTED -> RELEASED transition, but says nothing about irreversibility, permissions, or failure modes when the deal is in another state.

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 compact sentence with the effect and the state transition front-loaded and zero redundant wording. Nothing to trim and nothing buried.

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?

With an output schema present and rich annotations plus full schema coverage, the description need only convey the action and its effect, which it does. The one gap is precondition/error behavior, which matters for a destructive fund-releasing call but is partially implied by the state notation.

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 coverage is 100% and both parameters are documented in the schema itself, including the replay-is-a-no-op semantics of idempotency_key. The description adds no parameter-level meaning beyond what the schema already provides, so the 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?

Names a specific action on a specific resource ('Accept submitted proof') plus the concrete effect ('release funds') and the exact state transition (PROOF_SUBMITTED -> RELEASED). An agent can tell this apart from submit_proof at a glance; it does not, however, explicitly distinguish itself from confirm_deal or agree_deal.

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 state transition implies a precondition (proof must already be SUBMITTED) and the effect implies a terminal action, but the description never states when to call this versus confirm_deal, agree_deal, or dispute_deal. Usage is inferable from the state machine rather than taught.

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