Skip to main content
Glama

create_work_quote_acceptance_challenge

Ask 402Mob for the exact EIP-191 message binding buyer, seller wallet, quote ID, quote hash, expiry, and exact Base USDC amount. This is quote acceptance only; the payment requires a separate x402 authorization.

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": {
      "ticketId": "<ticketId>",
      "buyer": "<buyer>"
    },
    "name": "create_work_quote_acceptance_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A3.5/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 usefully discloses the exact payload the message will bind and that this step has no payment side effect, which is meaningful behavioral context. It does not say whether the call is read-only/idempotent, whether the challenge expires, or what the caller receives back.

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 tight sentences, front-loaded with the action and payload, then the scope caveat. No filler or redundancy.

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 two-required-parameter challenge endpoint with no annotations and no output schema, the description covers what the challenge represents and its separation from payment. It leaves the two inputs unexplained and gives no hint about the shape of the returned message, which is the minimum an agent needs to use it confidently.

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%, so the description must explain ticketId and buyer. It never mentions ticketId at all, and 'buyer' appears only as a field inside the signed message, not as the address that will sign. The link between the two required inputs and the returned challenge is left for the agent to infer.

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 concrete action (requesting an exact EIP-191 message from 402Mob) and enumerates what that message binds: buyer, seller wallet, quote ID, quote hash, expiry, and Base USDC amount. It also distinguishes itself from the payment step, which separates it from siblings like pay_work_ticket_quote. It never literally says it 'creates a challenge', but the intent is unambiguous.

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?

The second sentence gives an explicit boundary: 'This is quote acceptance only; the payment requires a separate x402 authorization.' That is real routing guidance for the accept-vs-pay decision an agent faces among these siblings. It stops short of stating preconditions (e.g. an accepted quote must already exist), so it is clear but not exhaustive.

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