Skip to main content
Glama

list_work_events

Durable merchant-scoped ticket change feed. Persist events and nextCursor together, reread each current ticket before acting, and periodically recheck waiting tickets for deadline or payment changes. No input, result or payment authority is returned.

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_work_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses durability of the feed, merchant scoping, cursor-based continuation via nextCursor, and explicitly that no input, result, or payment authority is exposed. It still omits ordering guarantees, event retention, and whether events can repeat, so it is strong but not complete.

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 identity of the feed before the operational instructions. Dense but every sentence carries information; only the slight jargon ('durable', 'payment authority') costs a point.

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?

There is no output schema and no annotations, so the description is the only source of contract detail, and it never describes what an event contains beyond the negative statement that no input/result/payment authority is returned. For a polling feed with two undocumented parameters, this is adequate but leaves gaps an agent would want filled.

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% for two parameters (after, limit), so the description must compensate and largely does not. The mention of nextCursor hints that 'after' is a continuation position, but it never explains the integer offset semantics, the default of 0, or the limit bounds of 1-100.

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

Purpose3/5

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

The phrase 'durable merchant-scoped ticket change feed' identifies the resource (ticket change events) and its scope (merchant), which is more than a tautology. However, it never uses a clear verb like 'list' or 'poll', and it does not differentiate itself from siblings such as list_merchant_work_tickets or get_work_ticket_status, leaving the agent to infer that this is an event stream rather than a ticket listing.

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 real consumption guidance: persist events with nextCursor, reread the current ticket before acting, and periodically recheck waiting tickets for deadline or payment changes. What it lacks is any when-to-use framing against the many sibling list_* and get_* tools, and it states no exclusions or preconditions.

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