Skip to main content
Glama

create_work_receipt_challenge

Create an EIP-191 challenge for the buyer to record accepted or disputed judgment of the retained result. 402Mob stores the signed receipt but does not arbitrate or refund.

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>",
      "buyer": "<buyer>",
      "verdict": "<verdict>"
    },
    "name": "create_work_receipt_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
verdictYes
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/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 usefully discloses the signing flow and the important platform boundary ('stores the signed receipt but does not arbitrate or refund'), but omits whether calling it mutates durable state, whether the challenge expires, and any auth requirements.

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 tight sentences with the action front-loaded and the liability disclaimer second. Nothing is redundant, though 'retained result' is domain jargon left undefined for a first-time caller.

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?

For a challenge-creation tool with no output schema, the description should indicate what is returned (a signable challenge payload) and the next step. It implies a signature flow but does not state the return shape, challenge lifetime, or the follow-up submission tool, leaving gaps an agent must guess at.

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 0%, so the description must compensate. It gives meaning to two of three parameters by naming the buyer as signer and defining the verdict as 'accepted or disputed', but ticketId is never mentioned and no format or constraint hints are added beyond the schema's patterns and enum.

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 and resource ('Create an EIP-191 challenge') plus the business purpose (buyer records accepted or disputed judgment of the retained result). An agent can distinguish this from create_work_result_challenge or create_delivery_receipt_challenge by the 'retained result' framing, though the description never explicitly contrasts them.

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: the challenge exists so the buyer can record a verdict on a retained result. There is no explicit statement of when to call this versus create_delivery_receipt_challenge or that submit_work_receipt must follow, and no prerequisites (e.g., result must already be retained) are spelled out.

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