Skip to main content
Glama

get_work_ticket_status

Read public recovery status for a buyer's work ticket, including state, readable quote terms, payment reference, and result hash. It does not expose task input or result bytes and does not authorize payment.

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>"
    },
    "name": "get_work_ticket_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/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 well: it declares the operation read-only and public, bounds the data disclosed (no task input, no result bytes), and clarifies that reading status has no payment side effect. It omits auth/visibility requirements and error behavior for unknown or inaccessible ticket IDs.

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?

Two sentences, front-loaded with the core action and result contents, followed by negative boundaries. No filler; every clause conveys scope or constraint.

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?

No output schema exists, so the description properly enumerates the returned fields rather than deferring to structured data, and it clarifies the exclusion of result bytes. For a single-parameter read tool this is nearly complete; only access/permission context for buyers is unstated.

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?

Only one parameter (ticketId) exists and the schema gives it no description text, so the description must compensate. It only implies that the ticket belongs to a buyer; it adds nothing about the UUID format, expected provenance, or what happens for an invalid or foreign ticket ID.

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 a specific verb and resource ("Read public recovery status for a buyer's work ticket") and enumerates what comes back: state, readable quote terms, payment reference, result hash. The clause "does not expose task input or result bytes" implicitly separates it from the result-reading sibling, though no sibling is named.

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?

Usage is implied by the word "recovery status" and by the explicit note that this read does not authorize payment, but there is no explicit when-to-use statement, no prerequisite conditions (e.g., who may read it), and no named alternative for callers who actually want result bytes.

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