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 durableticket_idimmediately, 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-channelfeedback_resolvedevent automatically. Ticket status remains readable before that notification arrives.ticket_idandaction: "resolve"→ resolves a ticket the caller submitted. This cannot resolve another submitter's ticket. An authenticated platform admin may also passresponseto write the customer-facing reply and resolve the ticket atomically.ticket_id(no message) → reads that one ticket. Returns itsstatus(open / investigating / resolved) andresponse(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
statusfilter 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
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | List mode. Optional. Max tickets to return (default 50, max 200). | |
| action | No | Resolve mode. "resolve" with ticket_id closes a support ticket the caller submitted. Admins may add response to reply and close atomically. | |
| status | No | List mode. Optional filter: open, investigating, or resolved. Without message and ticket_id, the tickets the caller submitted are listed. | |
| context | No | Submit mode. Optional structured context — endpoint, file size, error code, anything reproducible. Free-form JSON, up to 16KB. | |
| message | No | Submit mode. The support-ticket details — be specific: what you tried, what you expected, what happened. Up to 8000 chars. | |
| response | No | Admin 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_id | No | Submit 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_id | No | Check or resolve mode. A ticket id returned by a prior submit. Not combined with message. | |
| project_id | No | Submit mode. Optional. Project the support ticket relates to (UUID, subdomain, or "default"). |