Skip to main content
Glama

create_work_result_challenge

Create the buyer's short-lived EIP-191 authorization to retrieve the result with the stated hash. Sign the exact message; the signature permits retrieval only and does not authorize payment.

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>"
    },
    "name": "create_work_result_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/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 and does deliver real substance: short-lived lifetime, EIP-191 signing requirement, sign-the-exact-message constraint, and the crucial scope limit that the signature grants retrieval only and no payment authority. Still missing are single-use/replay semantics, whether the buyer key must be local, and what the tool returns for the agent to sign.

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 and the security scope front-loaded and no filler. The only blemish is the dangling 'stated hash' reference, which costs clarity rather than length.

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 two-param challenge-minting tool with no annotations and no output schema, the security semantics are well covered but the mechanics are not: nothing says what is returned (presumably a message to sign), how to follow up, or what the parameters mean.

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 coverage is 0% and only two parameters exist, yet the description never explains ticketId or buyer. Worse, it references 'the stated hash' while no hash parameter exists in the schema, leaving the agent to guess where that value comes from.

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?

Specific verb plus resource: creates the buyer's EIP-191 authorization to retrieve a result. The phrase 'to retrieve the result' distinguishes it from the receipt/grant/quote-acceptance challenge siblings, though it never names them explicitly.

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 implied rather than stated: the agent infers this is the step before result retrieval, and 'does not authorize payment' implicitly separates it from payment-path tools. There is no explicit when-to-use clause or reference to read_work_ticket_result or any other sibling.

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