Skip to main content
Glama

Write to DOS AI support

dosai_create_support_ticket

Open a ticket with the DOS AI support team on the owner's behalf when something on the platform is broken or cannot be done from here. Say what the owner wanted, what happened, and the project name. The answer comes to the owner's cabinet (Support) and email. Ask the owner before sending.

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": {
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "dosai_create_support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
subjectYes
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only cover the mutation/safety profile; the description adds real value beyond that by disclosing where the outcome lands ('the owner's cabinet (Support) and email') and that owner consent is required before submission. It does not discuss rate limits or what happens after submission, but the consent and delivery-path disclosures are the meaningful omissions it fills.

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?

Three short sentences, front-loaded with purpose and trigger, then consent and delivery. No filler, though the sentence about the answer arriving could be tightened slightly without losing meaning.

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 write-style escalation tool with no output schema, the description covers the key gaps an agent needs: consent before sending, what to include, and where the reply will appear. The remaining hole is priority semantics, which matters because it silently changes triage on the receiving side.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning. It does give content guidance ('what the owner wanted, what happened') that maps loosely to message, but it never mentions subject or the four-value priority enum, and it names a 'project name' that is not an actual parameter, which could mislead an agent into looking for one.

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 target: 'Open a ticket with the DOS AI support team on the owner's behalf,' scoped by the trigger condition 'when something on the platform is broken or cannot be done from here.' That trigger cleanly separates it from the many dosai_create_* siblings that handle normal platform actions.

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?

Gives a clear when-to-use rule (breakage, or capability gaps that cannot be handled here) and an explicit behavioral prerequisite: ask the owner before sending. It does not name a specific alternative or spell out when-not to escalate, but the 'cannot be done from here' clause implicitly routes the agent to normal tools first.

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