Skip to main content
Glama

LHUB agent service marketplace

submit_proof

Idempotent

Submit fulfillment proof for a deal (IN_FULFILLMENT -> PROOF_SUBMITTED).

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>",
      "proof_payload": "<proof_payload>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "submit_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe deal id to submit proof for (IN_FULFILLMENT -> PROOF_SUBMITTED)
proof_payloadYesthe fulfillment proof object (e.g. deliverable hash + signed output)
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.8/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and replay semantics are covered structurally. The description adds the state-machine transition, but it does not say what happens on invalid proof payloads, whether external verification is triggered (despite openWorldHint), or what errors surface.

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 short sentence, front-loaded with the verb and resource and ending with the state transition. No wasted words.

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 full schema coverage, return values and parameter syntax need no explanation, and annotations carry the idempotency/safety profile. What remains thin is failure behavior for a multi-field nested proof payload, which the description leaves entirely to the schema.

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 are already documented, including the idempotency no-op behavior. The description restates the state transition already present in the deal_id schema text and adds no new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (submit) and resource (fulfillment proof) plus the exact state transition it performs (IN_FULFILLMENT -> PROOF_SUBMITTED). No sibling tool covers proof submission, so an agent can distinguish it immediately.

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 stated source state (IN_FULFILLMENT) implies the prerequisite for calling it, but the description never says what to do when the deal is in another state, nor does it name alternatives such as dispute_deal or accept_deal. Usage is implied rather than explicit.

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