Skip to main content
Glama

quote_work_ticket

Submit one fixed quote after claiming a ticket. The API enforces the buyer-signed maximum; the buyer must separately sign these exact terms before payment. Requires merchant:work scope.

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>",
      "priceUSDC": "<priceUSDC>",
      "deliverable": "<deliverable>",
      "contentType": "<contentType>",
      "expiresInSeconds": "<expiresInSeconds>"
    },
    "name": "quote_work_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
priceUSDCYes
contentTypeYes
deliverableYes1–300 Unicode code points after trimming.
expiresInSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / deliverable / description
      Added value: +"1–300 Unicode code points after trimming."
    • changedInput schema / properties / priceUSDC / 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})?$"
  2. 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 discloses important behavior: the API enforces the buyer-signed maximum, the buyer must separately sign the exact terms before payment, and merchant:work scope is required. It does not cover idempotency, response format, or what happens if a quote already exists, but it adds substantial context beyond the schema.

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 three tight sentences with no wasted wording. The core action and prerequisite are front-loaded, followed by critical constraints and authorization scope.

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 five-parameter mutation tool with no annotations and no output schema, the description covers purpose, prerequisite, authorization, and key signing constraints. However, it leaves parameter semantics largely unexplained and does not describe the response or post-submission behavior, so it is adequate but incomplete.

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 20%, with just the deliverable field documented in the schema. The description does not explain ticketId, priceUSDC, contentType, or expiresInSeconds, and only indirectly hints that priceUSDC is bounded by the buyer-signed maximum. 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?

The description states a specific verb and resource: "Submit one fixed quote after claiming a ticket." It also gives the prerequisite of claiming a ticket, which helps distinguish it from claim_work_ticket. However, it does not explicitly differentiate from sibling tools like accept_work_ticket_quote or pay_work_ticket_quote.

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 description gives a clear prerequisite ("after claiming a ticket") and an authorization requirement ("Requires merchant:work scope"). It does not state when not to use this tool or name alternatives for accepting or paying a quote, so guidance is implied rather than explicit.

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