Skip to main content
Glama

read_work_ticket_result

Retrieve a retained ticket result using the buyer's signed result challenge. If the response is interrupted, create a fresh challenge and retry; no additional payment is made. Success includes exact delivery.bodyBase64 bytes and their verified SHA-256.

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

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. Changed1 schema field changed
    • changedInput schema / properties / signature / pattern
      Previous value: -"^0x(?:[0-9a-fA-F]{128}|[0-9a-fA-F]{130})$"New value: +"^0x[0-9a-fA-F]{130}$"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the retry/idempotency behavior, that retries incur no extra payment, and that a successful read returns exact delivery.bodyBase64 bytes with a verified SHA-256. It omits whether the retained result can expire and says nothing about failure modes beyond interruption.

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?

Three tight sentences, front-loaded with the core action, then the retry rule, then the success payload. No filler or redundant restatement of the tool name.

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?

For a three-required-parameter read tool with no annotations and no output schema, the description covers purpose, retry semantics, cost implications, and the shape of a successful return. Missing only edge details such as result retention/expiry and error responses.

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 implies challengeId/signature belong to a buyer-signed result challenge and ticketId identifies the ticket. However, it adds nothing about the signature format (0x-prefixed 130-hex value) or the UUID constraints, so half the parameter meaning is still only in the schema patterns.

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 ('Retrieve a retained ticket result') plus the mechanism ('buyer's signed result challenge'), which clearly separates it from the sibling submit_work_ticket_result. It stops short of naming an alternative tool outright, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage scenario and recovery path: if the response is interrupted, create a fresh challenge and retry, with the reassurance that no additional payment is made. It does not explicitly state prerequisites (e.g. that a challenge must exist first) or name the sibling used to create that challenge, leaving some inference to the agent.

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