Skip to main content
Glama

complete_work_request

Finish publishing a buyer request, not completing a worker job. First call create_work_request_challenge, sign its exact message locally, then submit all original request fields and idempotencyKey plus challengeId and signature. No payment is authorized.

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": {
      "buyer": "<buyer>",
      "title": "<title>",
      "description": "<description>",
      "maxPriceUSDC": "<maxPriceUSDC>",
      "contentType": "<contentType>",
      "expiresInSeconds": "<expiresInSeconds>",
      "acceptanceCriteria": "<acceptanceCriteria>",
      "idempotencyKey": "<idempotencyKey>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "complete_work_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
titleYesPublic untrusted text; at most 100 Unicode code points after trimming.
signatureYes
challengeIdYes
contentTypeYes
descriptionYesPublic untrusted text; at most 2000 Unicode code points after trimming.
maxPriceUSDCYes
idempotencyKeyYes
expiresInSecondsYes
acceptanceCriteriaYes
supersedesRequestIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / supersedesRequestId
      Added value: +{
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Added

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add valuable context — the two-phase challenge/signature requirement, replay-safety via idempotencyKey, and 'No payment is authorized' — but says nothing about what the call returns, what happens on a replayed idempotencyKey, or how signature/challenge failures surface, which matters for a mutating 10-required-param call.

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: disambiguation first, procedural sequence second, safety note last. No restatement of the name, no filler, and the most decision-relevant content is front-loaded.

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?

The flow, the challenge/signature trio, and the non-payment guarantee are covered, but for a 10-required-param mutation with no annotations and no output schema, the definition leaves gaps: the semantics of supersedesRequestId, the units/precision of maxPriceUSDC, and any indication of the success response are absent.

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?

With only 18% schema description coverage across 11 params, the description must compensate, and it partially does by grouping parameters: 'all original request fields and idempotencyKey plus challengeId and signature', which tells the agent the request fields are copied from the earlier creation call and the three are new. Format and meaning of maxPriceUSDC, expiresInSeconds bounds, contentType enum, acceptanceCriteria, and supersedesRequestId are left entirely to the schema.

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?

Opens with a specific verb+resource ('Finish publishing a buyer request') and explicitly negates a plausible misreading ('not completing a worker job'), which an agent could easily conflate with sibling complete_work_ticket_grant or accept_work_ticket_quote. It does not, however, distinguish itself from the very similarly named sibling complete_buyer_request, leaving one ambiguity unresolved.

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 an explicit ordering contract: call create_work_request_challenge first, sign its exact message locally, then submit. That sequencing is exactly the when-to-use context an agent needs. It stops short of stating exclusions or which sibling to pick if the caller has no challengeId yet.

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