Skip to main content
Glama

support_ticket

Support tickets for the Somewhere platform team — submit, check, list, or resolve your own tickets. For reports about the platform itself: a doc gap, an unexpected error shape, a missing capability, a bug in an MCP tool, or an inconsistency between docs and behavior. Not for feedback on a user's own app — that's the feedback tool.

Four modes, by argument:

  • message → submits a new support ticket. Returns a durable ticket_id immediately, stores the raw ticket in the support inbox, and notifies the team. The team replies on that same ticket. When the team records a reply or resolves the ticket, the reporting developer receives an email and a developer-channel feedback_resolved event automatically. Ticket status remains readable before that notification arrives.

  • ticket_id and action: "resolve" → resolves a ticket the caller submitted. This cannot resolve another submitter's ticket. An authenticated platform admin may also pass response to write the customer-facing reply and resolve the ticket atomically.

  • ticket_id (no message) → reads that one ticket. Returns its status (open / investigating / resolved) and response (the team's reply, once written).

  • Neither → lists the tickets the caller submitted, most recent first (open and resolved), each with status, response, and resolution timestamp. A status filter narrows the list.

Example:

// Submit:
{
  "message": "PUT /v1/fs binary upload returns 200 but reads back as UTF-8-replaced bytes — every byte ≥0x80 becomes EF BF BD. Reproed with curl --data-binary @cat.jpg.",
  "context": { "endpoint": "PUT /v1/fs", "file_size": 82823, "tried": ["binary_files base64 (worked)"] }
}

// Check one ticket:
{ "ticket_id": "pfb_a1b2c3d4e5f6" }

// Resolve your own ticket:
{ "ticket_id": "pfb_a1b2c3d4e5f6", "action": "resolve" }

// Admin reply + resolve:
{ "ticket_id": "pfb_a1b2c3d4e5f6", "action": "resolve", "response": "This is fixed and live. No action needed." }

// List open tickets:
{ "status": "open", "limit": 20 }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoList mode. Optional. Max tickets to return (default 50, max 200).
actionNoResolve mode. "resolve" with ticket_id closes a support ticket the caller submitted. Admins may add response to reply and close atomically.
statusNoList mode. Optional filter: open, investigating, or resolved. Without message and ticket_id, the tickets the caller submitted are listed.
contextNoSubmit mode. Optional structured context — endpoint, file size, error code, anything reproducible. Free-form JSON, up to 16KB.
messageNoSubmit mode. The support-ticket details — be specific: what you tried, what you expected, what happened. Up to 8000 chars.
responseNoAdmin resolve mode only. Written customer-facing reply to store and send while resolving the ticket atomically. Regular submitters should omit this and keep using action: "resolve" unchanged.
parent_idNoSubmit mode. Optional. The one narrowed task this ticket is about. Multiple tickets may link to the same task; its shipped version closes the linked tickets.
ticket_idNoCheck or resolve mode. A ticket id returned by a prior submit. Not combined with message.
project_idNoSubmit mode. Optional. Project the support ticket relates to (UUID, subdomain, or "default").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description goes well past that. It discloses side effects (durable `ticket_id`, raw ticket stored in the support inbox, team notified, email plus `feedback_resolved` developer-channel event on reply) and an authorization boundary (you cannot resolve another submitter's ticket; only an authenticated platform admin may pass `response`).

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?

It is long, but it is front-loaded with the mode table before the examples, and each paragraph maps to a distinct calling mode. The five JSON example blocks are somewhat heavy for the information they carry, which keeps it below a top mark for economy.

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?

With 9 loosely coupled parameters, no required fields, and no output schema, the description carries the full burden and meets it: it states what submit returns (`ticket_id`), what a read returns (`status`, `response`), what a list returns (status, response, resolution timestamp, ordering), and the auth requirement for admin replies. An agent can select and invoke every mode correctly from this text alone.

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, but the description adds genuine value the schema cannot: it explains that argument combinations select the mode, that `status` narrows the list, that list order is most-recent-first, and that status values are open / investigating / resolved. It also clarifies the admin-only atomic reply-and-resolve use of `response` and shows a realistic `context` payload.

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?

The description names the resource (support tickets for the Somewhere platform team) and the concrete operations (submit, check, list, resolve) in the first sentence, then scopes the subject matter to platform defects, doc gaps, and tool bugs. It explicitly distinguishes itself from the `feedback` sibling, which covers feedback on a user's own app.

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

Usage Guidelines5/5

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

The 'Four modes, by argument' block gives explicit when-to-use routing for each combination: `message` submits, `ticket_id` + `action: "resolve"` resolves, bare `ticket_id` reads one, neither lists. It also states a negative case ('**Not** for feedback on a user's own app') and names the alternative tool, plus the admin-only constraint on `response`.

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