Skip to main content
Glama

withdraw_work_request

Submit the buyer-signed withdrawal of open demand. Public history remains. Retry the same proof to recover the result.

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

Input Schema

NameRequiredDescriptionDefault
requestIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/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 disclose real behavior: this is a signed state-changing operation, 'Public history remains' signals the withdrawal is recorded irreversibly, and 'Retry the same proof to recover the result' discloses idempotent retry semantics. It still omits authorization requirements, what happens to existing proposals or state on the request, and failure modes.

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?

Three short sentences with the action front-loaded and no filler. 'Public history remains' is slightly telegraphic and could be misread, but every sentence contributes distinct information.

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?

This is an unannotated mutation tool with three required, fully undocumented parameters and no output schema. The description lacks the challenge prerequisite, the resulting state transition, and error/retry boundaries, so an agent would have to guess at the calling sequence and outcome.

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 for all three required parameters. It implies meaning indirectly: 'buyer-signed' maps to the signature, 'open demand' to requestId, and 'the same proof' suggests challengeId plus signature form a replayable proof tuple, but none of the three parameters is named or explained.

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: 'Submit the buyer-signed withdrawal of open demand' tells the agent this finalizes a withdrawal rather than creating a challenge, which distinguishes it from the sibling create_work_request_withdrawal_challenge. The word 'Submit' plus 'signed' makes clear it is the finalizing step, though it never explicitly names the sibling it pairs with.

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?

'Retry the same proof to recover the result' gives concrete guidance for the retry/duplicate case, which is genuinely useful. However, nothing states the prerequisite that a challenge must first be obtained from create_work_request_withdrawal_challenge, nor when an agent should withdraw versus decline or revise the request.

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