Skip to main content
Glama

read_work_execution

Privately recover the selected request's linked ticket using the buyer's read signature. Retry the original grant, never invent another payment authorization.

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

Input Schema

NameRequiredDescriptionDefault
requestIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add real behavioral context: access is 'privately' scoped, authorization comes from 'the buyer's read signature', and the agent is told not to fabricate a new payment authorization. That is useful auth and misuse information beyond the bare schema. It still does not state whether the call mutates state, what happens on signature failure, or whether retries are idempotent, which matters for a signature-gated tool.

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 short sentences with no filler, and the retrieval action is front-loaded ahead of the cautionary sentence. The economy is undercut slightly by cryptic phrasing ('linked ticket', 'the original grant') that forces interpretation, but there is no redundant or bloated wording.

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-required-parameter, signature-gated tool with no annotations and no output schema, the description leaves too much open: the challenge/signature flow is unexplained, the meaning of challengeId is absent, and there is no hint of what the returned ticket contains. An agent would have to guess at the prerequisite sequence before it could call this correctly.

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% across three required parameters, so the description must compensate, and it only partially does: 'selected request' gestures at requestId and 'buyer's read signature' clarifies whose signature the signature field expects. The challengeId parameter is never explained in the description or the schema, leaving a required UUID with no documented origin or purpose.

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

Purpose3/5

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

It names a verb plus an object ('recover the selected request's linked ticket'), which is more specific than a restatement of the name, but 'recover' and 'linked ticket' are metaphorical rather than concrete about what is retrieved. It gives no contrast to nearby siblings such as read_work_ticket_result or get_work_request, so an agent cannot confidently distinguish this read from those.

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

Usage Guidelines2/5

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

The only guidance is a constraint ('Retry the original grant, never invent another payment authorization'), which is a warning about misuse rather than a statement of when to call this tool. Nothing indicates the prerequisite of obtaining a challenge from create_work_execution_read_challenge, nor when to prefer read_work_ticket_result instead.

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