Galatic.ai

Contact support

create_support_ticket

Send a message to Galatic.AI support. Stores a ticket linked to the signed-in user, emails a confirmation to email and notifies the support team; returns { ticketId, emailSent }. message must be under 5000 characters; category defaults to "general". Use list_my_tickets to see earlier tickets. The message goes to people, so do not send it without the user asking.

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

Input Schema

Name	Required	Description
`name`	Yes
`email`	Yes	Where the confirmation email goes.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`message`	Yes	Under 5000 characters.
`category`	No	Defaults to "general".
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026
- addedInput schema / properties / category / description
```
Added value: +"Defaults to \"general\"."
```
- addedInput schema / properties / email / description
```
Added value: +"Where the confirmation email goes."
```
- addedInput schema / properties / message / description
```
Added value: +"Under 5000 characters."
```
First observedOct 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false, openWorld=false. The description goes well beyond them by disclosing side effects the schema cannot express: a ticket is persisted, an email is sent, support staff are notified, and the return payload is { ticketId, emailSent }. It also discloses the non-idempotence implication indirectly (each call messages people) and a consent constraint.

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?

Four short clauses, front-loaded with the action and its effects before the constraints and the sibling pointer. Every sentence carries information (effects, limits, alternative, consent rule); nothing is padding.

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 7-parameter mutation tool with 86% schema coverage and no output schema, the description still supplies the return shape ({ ticketId, emailSent }) and the human-facing consequences of calling it. Combined with the annotations, an agent has enough to call it correctly and safely.

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 86%, so the schema already documents email, context, message, category, llm_model, and conversation_id. The description only restates the 5000-character limit and the 'general' default for category, both of which are already in the schema. No additional meaning is added for the required but undocumented name or the conversation_id lifecycle.

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 ('Send a message to Galatic.AI support') and then enumerates the concrete effects: creates a stored ticket tied to the signed-in user, sends a confirmation email, notifies the support team. It explicitly contrasts itself with list_my_tickets, so an agent can separate it from the read-only siblings.

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?

Gives both a routing rule ('Use list_my_tickets to see earlier tickets') and an exclusion of the form 'do not send it without the user asking', which is the key precondition for a message that reaches humans. No inference is required about when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.