Skip to main content
Glama

submit_work_ticket_result

Submit a bounded result after the ticket payment is confirmed. Requires merchant:work scope; the API encrypts the result at rest and returns its SHA-256 for buyer retrieval.

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>",
      "contentType": "<contentType>",
      "result": "<result>"
    },
    "name": "submit_work_ticket_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultYes
ticketIdYes
contentTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  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 does substantial work: it names the required merchant:work scope, discloses server-side encryption at rest, and states that a SHA-256 digest is returned for buyer retrieval. Gaps remain on irreversibility and what 'bounded' enforces, but the key non-obvious behaviors are surfaced.

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?

Two tight sentences with the lifecycle precondition and the outcome front-loaded. No filler, and the scope requirement and return value are packed into the same span without padding.

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?

The tool has no annotations and no output schema, so the description needs to cover both safety profile and return value; it does cover encryption and the SHA-256 return, which is good. But it leaves the three required parameters undocumented and never defines the bound on the result payload, which is the central constraint of the operation.

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%, so the description must explain ticketId, contentType, and result. It explains none of them explicitly; 'bounded result' hints at a size limit for 'result' but gives no limit, and the contentType enum choices go entirely unexplained.

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 ('Submit a bounded result') and anchors it to a clear lifecycle precondition ('after the ticket payment is confirmed'). An agent can distinguish it from read_work_ticket_result by the verb, but the description never names the sibling it replaces or how it differs from submit_work_receipt.

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 payment-confirmed precondition is a real usage gate that tells the agent when this call is valid. However, there is no guidance about what to do if payment is not yet confirmed, whether submission can be repeated, or which sibling to use for reading back the result.

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