Skip to main content
Glama

list_merchant_work_tickets

Seller inbox. Requires a merchant API bearer key with merchant:work scope. Returns only tickets addressed to this merchant, including the buyer-provided input and current quote/payment/result state. order=latest reads newest created first; default oldest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_merchant_work_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • addedInput schema / properties / order
      Added value: +{
      +  "enum": [
      +    "oldest",
      +    "latest"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and does well: it discloses the auth scope required, the strict merchant-scoping filter, what each returned ticket contains (buyer input plus quote/payment/result state), and the default sort direction. It stops short of describing pagination or what happens when limit is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the resource identity and then the access requirement and return shape. The 'Seller inbox' opener is slightly metaphorical but is immediately grounded by the concrete sentence that follows; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list with no output schema, the description supplies auth, scope, return contents and ordering defaults — enough to call it correctly. The uncovered limit parameter (default and 50-item cap) is the one meaningful omission.

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 coverage is 0%, so the description must compensate. It explains order semantics well ('order=latest reads newest created first; default oldest'), adding meaning beyond the bare enum, but says nothing about limit — its default, or that it caps at 50 — leaving half the parameters to inference.

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 the resource and scope concretely: 'Returns only tickets addressed to this merchant, including the buyer-provided input and current quote/payment/result state.' The 'Seller inbox' framing plus the merchant-only scope implicitly separates it from buyer-side siblings like list_work_requests, though it never names an alternative outright.

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 the key operational prerequisite (merchant API bearer key with merchant:work scope) and clarifies which ordering to pick via order=latest. It does not say when to prefer this over a sibling such as get_work_ticket_status for a single ticket, so usage is implied rather than fully guided.

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