Skip to main content
Glama
topotal

Waroom MCP

by topotal

waroom_update_incident_labels

Add or update labels on incidents in Waroom MCP to categorize and organize incident data for better tracking and analysis.

Instructions

インシデントにラベルを付与または更新します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incident_uuidYes対象インシデントのUUID
label_uuidsYes付与するラベルのUUID配列

Implementation Reference

  • The handler function that executes the tool logic: calls WaroomClient.updateIncidentLabels with provided parameters and returns the JSON response or an error message in MCP format.
      async (params) => {
        try {
          const response = await waroomClient.updateIncidentLabels(
            params.incident_uuid,
            params.label_uuids
          );
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(response, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `インシデントラベルの更新に失敗しました: ${error}`
            }]
          };
        }
      }
    );
  • Zod schema defining the input parameters for the tool: incident_uuid (UUID string) and label_uuids (array of UUID strings).
    {
      incident_uuid: z.string().uuid().describe('対象インシデントのUUID'),
      label_uuids: z.array(z.string().uuid()).describe('付与するラベルのUUID配列'),
    },
  • Registers the 'waroom_update_incident_labels' tool on the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
      'waroom_update_incident_labels',
      'インシデントにラベルを付与または更新します。',
      {
        incident_uuid: z.string().uuid().describe('対象インシデントのUUID'),
        label_uuids: z.array(z.string().uuid()).describe('付与するラベルのUUID配列'),
      },
      async (params) => {
        try {
          const response = await waroomClient.updateIncidentLabels(
            params.incident_uuid,
            params.label_uuids
          );
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(response, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `インシデントラベルの更新に失敗しました: ${error}`
            }]
          };
        }
      }
    );
  • The WaroomClient helper method that performs the actual API PATCH request to update labels on an incident.
    async updateIncidentLabels(incidentUuid: string, labelUuids: string[]) {
      try {
        const response = await this.axiosInstance.patch(`${this.baseUrl}/incidents/${incidentUuid}/labels`, {
          label_uuids: labelUuids
        });
        return response.data;
      } catch (error) {
        throw new Error(`Failed to update incident labels: ${error}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool assigns or updates labels on incidents, implying a mutation operation, but lacks details on permissions required, whether changes are reversible, rate limits, or what happens to existing labels not included in 'label_uuids'. 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?

The description is a single, efficient sentence in Japanese that directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to grasp quickly.

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 the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It fails to address behavioral aspects like error handling, response format, or interaction with sibling tools. For a tool that modifies incident labels, more context is needed to ensure safe and effective use.

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%, with both parameters ('incident_uuid' and 'label_uuids') well-documented in the schema. The description adds no additional meaning beyond the schema, such as explaining how label updates work (e.g., whether they replace or append). Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 action ('付与または更新します' - assign or update) and the resource ('インシデントにラベル' - labels on incidents), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'waroom_update_service_label' which also updates labels but on services rather than incidents, missing explicit differentiation.

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 like 'waroom_update_service_label' or other incident-related tools such as 'waroom_update_incident_severity' or 'waroom_update_incident_status'. The description implies usage for label management on incidents but offers no context on prerequisites, exclusions, or specific scenarios.

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