Skip to main content
Glama
topotal

Waroom MCP

by topotal

waroom_create_incident

Create incidents in Waroom by specifying service name, title, severity, and description to track and manage operational issues.

Instructions

インシデントを作成します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_nameYesサービス名またはサービスID
titleYesインシデントのタイトル(1-255文字)
severityYes重要度(critical, high, low, info, unknown)
descriptionYesインシデントの説明
experimentalNo実験的なインシデントかどうか(デフォルト: false)
is_privateNoプライベートインシデントかどうか(デフォルト: false)

Implementation Reference

  • The async handler that executes the waroom_create_incident tool logic by calling waroomClient.createIncident and returning the JSON response or error.
    async (params) => {
      try {
        const response = await waroomClient.createIncident(
          params.service_name,
          params.title,
          params.severity,
          params.description,
          params.experimental,
          params.is_private
        );
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `インシデントの作成に失敗しました: ${error}`
          }]
        };
      }
    }
  • Zod input schema defining parameters for the waroom_create_incident tool.
      service_name: z.string().min(1).describe('サービス名またはサービスID'),
      title: z.string().min(1).max(255).describe('インシデントのタイトル(1-255文字)'),
      severity: z.enum(['critical', 'high', 'low', 'info', 'unknown']).describe('重要度(critical, high, low, info, unknown)'),
      description: z.string().min(1).describe('インシデントの説明'),
      experimental: z.boolean().default(false).describe('実験的なインシデントかどうか(デフォルト: false)'),
      is_private: z.boolean().default(false).describe('プライベートインシデントかどうか(デフォルト: false)'),
    },
  • Registration of the waroom_create_incident tool using server.tool, including description, schema, and handler.
    server.tool(
      'waroom_create_incident',
      'インシデントを作成します。',
      {
        service_name: z.string().min(1).describe('サービス名またはサービスID'),
        title: z.string().min(1).max(255).describe('インシデントのタイトル(1-255文字)'),
        severity: z.enum(['critical', 'high', 'low', 'info', 'unknown']).describe('重要度(critical, high, low, info, unknown)'),
        description: z.string().min(1).describe('インシデントの説明'),
        experimental: z.boolean().default(false).describe('実験的なインシデントかどうか(デフォルト: false)'),
        is_private: z.boolean().default(false).describe('プライベートインシデントかどうか(デフォルト: false)'),
      },
      async (params) => {
        try {
          const response = await waroomClient.createIncident(
            params.service_name,
            params.title,
            params.severity,
            params.description,
            params.experimental,
            params.is_private
          );
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(response, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `インシデントの作成に失敗しました: ${error}`
            }]
          };
        }
      }
    );
  • src/main.ts:26-26 (registration)
    Top-level call to createIncidentsTools which registers the waroom_create_incident tool (and other incident tools).
    createIncidentsTools(server, waroomClient);
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Creates an incident' implies a write/mutation operation but doesn't disclose behavioral traits like permissions needed, whether creation is irreversible, rate limits, or what happens on success/failure. This is a significant gap for a mutation tool with zero annotation coverage.

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?

Extremely concise single sentence with zero waste. It's front-loaded with the core action, though this brevity comes at the cost of completeness.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects, usage context, or return values, leaving significant gaps for an AI agent to understand how to use it correctly.

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 100%, so the schema already documents all 6 parameters thoroughly. The description adds no meaning beyond what the schema provides (e.g., doesn't explain relationships between parameters or business logic). Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

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

The description 'インシデントを作成します' (Creates an incident) states a clear verb+resource but is vague about scope and doesn't differentiate from sibling tools like 'waroom_create_postmortem' or 'waroom_create_incident_metrics'. It doesn't specify what kind of incident or in what context.

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?

No guidance on when to use this tool versus alternatives like 'waroom_create_postmortem' or 'waroom_update_incident_status'. The description provides no context about prerequisites, timing, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/topotal/waroom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server