Skip to main content
Glama

claim_work_ticket

Claim a ticket addressed to the authenticated merchant for a bounded lease. Requires merchant:work scope and a bearer API key.

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": "claim_work_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
leaseSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/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 behavioral burden. It usefully discloses the merchant:work scope, bearer API key requirement, and bounded lease, but omits claim exclusivity/conflict behavior, lease expiry or renewal consequences, and response semantics.

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 two front-loaded sentences with no filler. Both the claim/lease scope and the authentication prerequisite earn their place.

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

Completeness2/5

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

There are no annotations, no output schema, and no parameter descriptions. For a lease-claim mutation tool, the definition should explain parameter meaning and claim conflict/return behavior; the current description gives purpose and auth context but is incomplete for safe invocation.

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%; the schema only constrains ticketId with a UUID pattern and leaseSeconds with min/max values. The description never explains ticketId, leaseSeconds, or any default lease duration, so it does not compensate for the missing schema documentation.

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: 'Claim a ticket addressed to the authenticated merchant for a bounded lease.' This distinguishes it from status/list/quote/accept siblings by scope and action, though it does not explicitly name any alternative tool.

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?

It implies usage by an authenticated merchant claiming its own addressed ticket and states the required scope, but gives no explicit when-to-use or when-not-to-use guidance versus siblings such as list_merchant_work_tickets or get_work_ticket_status.

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