Skip to main content
Glama
topotal

Waroom MCP

by topotal

waroom_create_incident_metrics

Create incident metrics to record response activities and update TTD/TTA/TTI/TTF/TTR values for incident tracking and analysis.

Instructions

インシデントメトリクスを作成します。レスポンス活動を記録し、TTD/TTA/TTI/TTF/TTRを更新します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incident_uuidYes対象インシデントのUUID
activity_actionYes活動アクション(status: detected/investigating/fixing/resolved/close/triggered, severity: critical/high/low/info/unknown, root_cause: unspecified/code_bug/configuration_error/deployment_failure/infrastructure_failure/operational_failure/third_party_outage/other)
triggered_atYes実行時刻(ISO 8601形式、例: 2023-01-01T12:00:00Z)

Implementation Reference

  • The handler function that executes the tool logic by calling WaroomClient.createIncidentMetrics and formatting the response as MCP content.
    async (params) => {
      try {
        const response = await waroomClient.createIncidentMetrics(
          params.incident_uuid,
          params.activity_action,
          params.triggered_at
        );
        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 tool: incident_uuid, activity_action, and triggered_at.
    {
      incident_uuid: z.string().uuid().describe('対象インシデントのUUID'),
      activity_action: z.enum(['detected', 'investigating', 'fixing', 'resolved', 'close', 'triggered', 'critical', 'high', 'low', 'info', 'unknown', 'unspecified', 'code_bug', 'configuration_error', 'deployment_failure', 'infrastructure_failure', 'operational_failure', 'third_party_outage', 'other']).describe('活動アクション(status: detected/investigating/fixing/resolved/close/triggered, severity: critical/high/low/info/unknown, root_cause: unspecified/code_bug/configuration_error/deployment_failure/infrastructure_failure/operational_failure/third_party_outage/other)'),
      triggered_at: z.string().regex(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{3})?([+-]\d{2}:\d{2}|Z)$/).describe('実行時刻(ISO 8601形式、例: 2023-01-01T12:00:00Z)'),
    },
  • src/main.ts:26-26 (registration)
    Top-level registration call that invokes createIncidentsTools to register the incidents tools group, including waroom_create_incident_metrics.
    createIncidentsTools(server, waroomClient);
  • Direct registration of the waroom_create_incident_metrics tool using server.tool, including description, schema, and handler.
    server.tool(
      'waroom_create_incident_metrics',
      'インシデントメトリクスを作成します。レスポンス活動を記録し、TTD/TTA/TTI/TTF/TTRを更新します。',
      {
        incident_uuid: z.string().uuid().describe('対象インシデントのUUID'),
        activity_action: z.enum(['detected', 'investigating', 'fixing', 'resolved', 'close', 'triggered', 'critical', 'high', 'low', 'info', 'unknown', 'unspecified', 'code_bug', 'configuration_error', 'deployment_failure', 'infrastructure_failure', 'operational_failure', 'third_party_outage', 'other']).describe('活動アクション(status: detected/investigating/fixing/resolved/close/triggered, severity: critical/high/low/info/unknown, root_cause: unspecified/code_bug/configuration_error/deployment_failure/infrastructure_failure/operational_failure/third_party_outage/other)'),
        triggered_at: z.string().regex(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{3})?([+-]\d{2}:\d{2}|Z)$/).describe('実行時刻(ISO 8601形式、例: 2023-01-01T12:00:00Z)'),
      },
      async (params) => {
        try {
          const response = await waroomClient.createIncidentMetrics(
            params.incident_uuid,
            params.activity_action,
            params.triggered_at
          );
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(response, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `インシデントメトリクスの作成に失敗しました: ${error}`
            }]
          };
        }
      }
    );
  • Supporting method in WaroomClient that performs the actual API call to create incident metrics.
    async createIncidentMetrics(incidentUuid: string, activityAction: string, triggeredAt: string) {
      try {
        const response = await this.axiosInstance.post(`${this.baseUrl}/incidents/${incidentUuid}/metrics`, {
          activity_action: activityAction,
          triggered_at: triggeredAt
        });
        return response.data;
      } catch (error) {
        throw new Error(`Failed to create incident metrics: ${error}`);
      }
    }
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. It mentions creating metrics and updating time metrics, implying a write operation, but doesn't disclose behavioral traits like permissions needed, whether it's idempotent, rate limits, or what happens on failure. This is inadequate 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.

Conciseness4/5

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

The description is concise with two sentences that efficiently state the purpose and key actions. It's front-loaded with the main function and avoids unnecessary details, though it could be slightly more structured by separating creation from update aspects.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error handling, or return values, and lacks usage guidance relative to siblings. For a tool that updates critical incident metrics, more context is needed.

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 three parameters thoroughly. The description adds no additional meaning beyond implying these parameters are used for creating metrics and updating time metrics, but doesn't explain how they relate semantically. 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.

Purpose4/5

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

The description clearly states the tool creates incident metrics and records response activities while updating specific time metrics (TTD/TTA/TTI/TTF/TTR). It specifies the verb 'creates' and resource 'incident metrics' but doesn't differentiate from siblings like waroom_create_incident or waroom_update_incident_status, which also involve incident operations.

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 is provided on when to use this tool versus alternatives. With siblings like waroom_update_incident_status and waroom_update_incident_severity that might overlap in incident management, the description lacks explicit context, prerequisites, or comparisons, leaving usage unclear.

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