Skip to main content
Glama

create_work_request_challenge

Create an exact EIP-191 challenge for public fresh-work demand and acceptance criteria. No payment or ticket 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>"
    },
    "name": "create_work_request_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
titleYesPublic untrusted text; at most 100 Unicode code points after trimming.
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

B3.2/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 behavioral burden. It usefully discloses that this creates an exact EIP-191 challenge and that no payment or ticket is authorized, but it omits important behavior such as idempotency handling, expiry semantics, supersession behavior, and what the challenge response represents.

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?

The description is two tight sentences with the core action front-loaded and a critical safety boundary immediately after. There is no wasted 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?

This is a complex 9-parameter creation tool with no annotations, no output schema, and low schema description coverage. The description gives purpose and a safety disclaimer but is far too sparse to fully prepare an agent for correct invocation.

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 only 22% across 9 parameters, so the description needs to compensate but largely does not. It references demand and acceptance criteria conceptually, but does not explain buyer, maxPriceUSDC, contentType, expiresInSeconds, idempotencyKey, or supersedesRequestId semantics.

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 states a specific verb and resource: create an EIP-191 challenge for public fresh-work demand and acceptance criteria. It is clear what the tool does, though it does not explicitly distinguish itself from the many sibling challenge-creation tools.

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?

The phrase 'for public fresh-work demand and acceptance criteria' implies the usage context, and 'No payment or ticket is authorized' clarifies a boundary. However, it does not explicitly say when to use this tool versus sibling challenge tools or what prerequisites apply.

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