Skip to main content
Glama

createSupportTicket

Open a FitsThis support ticket. Prefer orderId when known. If email matches the PayPal buyer on that order, the ticket opens immediately; otherwise status is pending_confirm and the human must open confirmUrl on fitsthis.com. Rate-limited. Prefer getOrderStatus first for tracking questions.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
emailYes
messageYes
orderIdNo
subjectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/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 so well: it discloses the conditional outcome (immediate open vs. status pending_confirm), the human follow-up step on confirmUrl at fitsthis.com, and that the tool is rate-limited. These are exactly the non-obvious behaviors an agent needs before invoking a mutation.

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?

Five short sentences, each carrying distinct information: purpose, parameter preference, conditional behavior, rate limit, and sibling routing. The conditional outcome is front-loaded before the rate-limit caveat, and there is no filler.

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?

For a five-parameter mutation tool with no annotations and no output schema, the description covers the risky parts: the confirmation flow, the rate limit, and the tracking-question alternative. It stops short of describing what the call returns (ticket id, confirmUrl field, status value), which an agent would need to act on the response.

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?

Schema description coverage is 0%, so the description must compensate, and it only partially does. It explains the semantics of email (PayPal buyer match) and the preference for orderId, but says nothing about kind's enum values, subject, or message constraints, leaving three of five parameters documented only by raw schema types.

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 opens with a specific verb and resource: 'Open a FitsThis support ticket', which is unambiguous. It is distinguishable from the admin siblings (adminGetTicket, adminReplyTicket, adminSetTicketStatus) by being the customer-initiated creation path, though it never explicitly contrasts itself with them.

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?

It gives concrete routing advice: prefer getOrderStatus first for tracking questions, and prefer orderId when known. That is real when-to-use guidance with a named alternative, but there is no explicit when-not-to-use or statement of prerequisites (e.g. that a human must act on confirmUrl in the pending path is stated, but not who should call this at all).

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