Skip to main content
Glama

submit_work_receipt

Store the buyer's signed accepted/disputed receipt for this result. Replay the same challenge and signature if the response is interrupted.

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": {
      "ticketId": "<ticketId>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "submit_work_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key trait that this is a mutation whose retry is safe if the same challenge and signature are replayed. It omits what the signature must attest to, whether the stored receipt is final/immutable, and what happens on a mismatched or expired challenge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact, front-loaded sentences with no filler; the retry instruction in the second sentence earns its place. 'For this result' is slightly loose wording given the parameter is named ticketId.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, mutation-style tool with no annotations and no output schema, the description should at minimum say how the challenge is created and what the caller gets back or what errors mean. It provides the retry semantics but leaves prerequisites and return behavior unaddressed.

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% and all three required parameters (ticketId, challengeId, signature) are documented only by name and format patterns. The description mentions 'challenge and signature' but never explains what ticketId identifies, how the challenge is obtained, or the expected signature scheme beyond the 0x-prefixed 130-hex pattern.

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 plus resource: 'Store the buyer's signed accepted/disputed receipt for this result', which tells an agent this is a write of a buyer-signed receipt tied to a result. It doesn't explicitly contrast with the sibling submit_delivery_receipt, so the distinction (work vs delivery receipts) still has to be inferred from the name.

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 only implied: call it to store a buyer receipt, and re-call with the same challenge and signature if a prior response was interrupted. There is no stated precondition (e.g. that a challenge must first be obtained via create_work_receipt_challenge) and no guidance on when not to use it versus sibling receipt tools.

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