Skip to main content
Glama

create_work_request_withdrawal_challenge

Prepare a buyer signature to withdraw unselected open demand. This cannot cancel selected work, a ticket, escrow or 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": {
      "requestId": "<requestId>",
      "buyer": "<buyer>"
    },
    "name": "create_work_request_withdrawal_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 does disclose that the tool produces a signature artifact rather than performing the withdrawal, and it explicitly bounds what it cannot affect (selected work, ticket, escrow, payment), which is valuable non-obvious context. It says nothing about permissions/authorization required, whether the challenge expires, or whether any state is mutated on creation.

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?

Two short sentences with no filler; the positive action comes first and the scope limits follow immediately.

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 small two-parameter tool with no output schema this is close to adequate, and the carve-outs add real value. It is still incomplete in that neither parameter is described and the agent is not told what the prepared signature/challenge looks like or what to do with it afterwards.

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% for two required parameters (requestId, buyer), so the description must compensate and largely fails to. 'Buyer signature' hints that buyer is the signing address, but neither parameter is named, and requestId — the key to which work request is being withdrawn — is never mentioned 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?

The description gives a specific verb ('Prepare a buyer signature') and resource ('to withdraw unselected open demand'), which is more precise than the name alone. It does not name or differentiate itself from the closely related sibling withdraw_work_request, so an agent must infer whether this is a prerequisite step or a replacement for it.

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: 'Prepare a buyer signature' suggests a two-step flow culminating in some submission/withdrawal, but no explicit 'use this before X' statement is given. The negative scope ('cannot cancel selected work, a ticket, escrow or payment') usefully rules out some cases where an agent might otherwise reach for this tool.

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