Skip to main content
Glama

accept_work_ticket_quote

Accept the exact current seller quote with its challenge-bound EIP-191 signature. This does not pay the seller. Next, call pay_work_ticket_quote using a separate exact 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>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "accept_work_ticket_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
signatureYes
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/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 meaningful behavior: the acceptance is signature-bound to a challenge, the quote must be the "exact current" one, and the call is non-paying with payment deferred to a separate tool. It does not state what state transition occurs, whether acceptance is idempotent or reversible, or what happens if the quote has changed since the challenge was issued.

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 sentences, no filler. The scope statement is front-loaded and the negative constraint ("does not pay the seller") immediately precedes the follow-up action, which is the ideal order for an agent planning a multi-step flow.

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?

No output schema and no annotations, so the description must cover what the tool returns and how it fails; it covers neither. The call sequence is well handled, but a mutation tool that consumes a signed challenge should at minimum indicate the resulting ticket state or the error shape for a stale/invalid signature.

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?

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It does map concepts onto all three — ticketId via "work ticket," challengeId via "challenge-bound," signature via "EIP-191" — but leaves the exact signature payload, the ticket/challenge relationship, and the "exact current" matching rule unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Accept the exact current seller quote") plus the required credential ("challenge-bound EIP-191 signature"). It explicitly draws the boundary against the adjacent sibling by noting "This does not pay the seller," so an agent can distinguish it from pay_work_ticket_quote without inspecting either schema.

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 clear sequencing: accept now, then call pay_work_ticket_quote with a separate authorization. What is missing is the upstream precondition — it never names create_work_quote_acceptance_challenge, which is presumably where the challengeId originates, so the agent must infer how to obtain the challenge.

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