Skip to main content
Glama

create_work_ticket_grant_challenge

Create a buyer-signed, ticket-specific budget grant. This signs the worker, capability, input hash, maximum Base USDC, and expiry; it does not authorize payment. Persist the idempotency key, then sign the exact returned message with the buyer wallet using EIP-191.

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>",
      "merchantId": "<merchantId>",
      "capability": "<capability>",
      "input": "<input>",
      "maxPriceUSDC": "<maxPriceUSDC>",
      "expiresInSeconds": "<expiresInSeconds>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_work_ticket_grant_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
inputYes
agreementNo
capabilityYes3–100 Unicode code points after trimming.
merchantIdYes
maxPriceUSDCYes
idempotencyKeyYes
expiresInSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agreement
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "proposalId": {
      +      "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"
      +    },
      +    "proposalTermsHash": {
      +      "pattern": "^[a-f0-9]{64}$",
      +      "type": "string"
      +    },
      +    "protocol": {
      +      "const": "402mob.work-agreement.v1",
      +      "type": "string"
      +    },
      +    "requestId": {
      +      "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"
      +    },
      +    "settlementMode": {
      +      "const": "direct_prepayment",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "protocol",
      +    "requestId",
      +    "proposalId",
      +    "proposalTermsHash",
      +    "settlementMode"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / capability / description
      Added value: +"3–100 Unicode code points after trimming."
    • changedInput schema / properties / maxPriceUSDC / pattern
      Previous value: -"^(?!0+(?:\\.0{1,6})?$)(?:0|[1-9][0-9]{0,17})(?:\\.[0-9]{1,6})?$"New value: +"^(?!0+(?:\\.0{1,6})?$)(?:0|[1-9][0-9]{0,5})(?:\\.[0-9]{1,6})?$"
  3. 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 important behavior: it returns a message to sign, lists the signed fields, says it does not authorize payment, and specifies idempotency-key persistence and EIP-191 signing. It leaves some side-effect and prerequisite details unstated, but adds substantial behavioral context.

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 sentences, front-loaded with the purpose and followed by the critical signing workflow. There is no filler, and every sentence contributes either scope or operational guidance.

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 description covers the main purpose and signing workflow for a complex eight-parameter tool. It still omits important required inputs such as merchantId and the agreement object, and does not clarify how the input object relates to the 'input hash' it says is signed.

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 13% for eight parameters, and the description mentions only some concepts such as capability, maximum Base USDC, expiry, and idempotency key. It loosely refers to 'worker' and 'input hash' while never explaining merchantId, the buyer address role, or the required nested agreement object, so it does not compensate for the low schema coverage.

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?

States a specific verb and resource: create a buyer-signed, ticket-specific budget grant. It also clarifies that this does not authorize payment, which helps distinguish it from payment-related siblings, but it does not explicitly differentiate it from challenge creators such as complete_work_ticket_grant.

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?

Provides useful post-call workflow guidance: persist the idempotency key and sign the exact returned message with the buyer wallet using EIP-191. However, it does not state when to choose this tool versus complete_work_ticket_grant or the other challenge-creation siblings.

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