Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Create Ticket

createTicket
Destructive

Submit a support ticket to Cloady with a subject and message details; the AI responds first while the team reviews every request.

Instructions

The AI answers the ticket first, and each new message from its author, until someone from the Cloady team replies. The team reads every ticket.

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": "createTicket"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.0
    • addedInput schema / properties / requestBody / properties / userId
      Added value: +{
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.5.1

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare a write operation (readOnlyHint=false, destructiveHint=true, openWorldHint=true). The description adds genuine context beyond those flags: an AI replies first, it also answers every subsequent author message, and a human team reads every ticket — useful for understanding visibility of the submitted content. However, it omits prerequisites (auth, workspace context), rate limits, and any note about what is created or returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, but the space is spent on post-submission behavior rather than the action itself, so it is concise without being front-loaded on the essential fact (that it opens a ticket).

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

Completeness2/5

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

For a create/mutation tool with a nested-object schema, open-world and destructive hints, and no output schema, the description should say what is created, what the caller must supply, and when to prefer contactSupport or addTicketMessage. Instead it covers only the follow-up conversation flow, leaving the core contract unexplained.

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 high, so the schema is the baseline documentation for the nested requestBody (subject, body, topic, userId). The description adds no meaning about any field — e.g., that userId ties the ticket to a specific author, or what topic is used for — so it neither helps nor harms beyond the 3 baseline.

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

Purpose2/5

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

The description never says the tool creates/submits a ticket; it describes what happens afterwards ('The AI answers the ticket first... The team reads every ticket'). An agent reading only the description would not learn the verb or that subject/body input is supplied, and would have to rely on the name and title to infer creation. It is closer to restating the tool's downstream effect than stating its action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no differentiation from relevant siblings such as contactSupport, listTickets, getTicket, or addTicketMessage. The only implied guidance is that opening a ticket starts an AI-answered conversation, which the agent must infer.

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

Deploy Server

Other Tools