Skip to main content
Glama

ticket_create

File a support ticket when something went wrong (a check, an order, payment, or printsi itself). With --order, the order's history is attached. A person reads every ticket; replies go to the email that paid for the order.

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": {
      "message": "<message>"
    },
    "name": "ticket_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoWhere to reply when there's no order (the user's own address, only with their permission). As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}.
orderNoThe order it's about (ord_…), if any.
messageYesWhat happened and what you expected (10–4000 characters). Include error codes and request ids.
subjectNoOne-line summary (defaults to the message's first line).
categoryNoOne of: order_problem, check_problem, payment, bug, question, other.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that supplying an order attaches that order's history, that a human reads every ticket (async, human-in-the-loop), and where the reply lands ('the email that paid for the order' rather than the filer's address). It does not address duplicate-submission risk, which matters given idempotentHint=false, but that annotation plus the human-review note covers most of the gap.

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 short sentences, front-loaded with the trigger condition and followed by the two facts an agent most needs before calling. The '--order' syntax is the one piece of noise that could confuse an agent reading a JSON parameter name.

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

Completeness5/5

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

For a create tool with an output schema, full parameter coverage, and explicit annotations, the description covers the remaining unknowns: when to file, what the order parameter does behaviorally, and how follow-up communication happens. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description still adds real semantics: it explains the side effect of the order parameter (history is attached) and clarifies reply routing, which the schema's email description only partially conveys. The '--order' flag notation is a CLI artifact that reads oddly in an MCP context but still maps unambiguously to the order parameter.

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

Purpose5/5

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

States a specific verb and resource ('File a support ticket') and narrows the domain with concrete examples of what counts as 'something went wrong' (check, order, payment, or printsi itself). This is clearly distinguishable from the read-side siblings ticket_list and ticket_show, which retrieve rather than file tickets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition ('when something went wrong') plus the categories of failure that qualify, which is enough for an agent to decide to call it. It stops short of explicit exclusions — e.g., when the issue is feedback rather than a problem, or when ticket_show should be used to check an existing ticket first.

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