Waroom MCP

waroom_create_incident_action_item

Create a new action item for a specified incident to track follow-up tasks. Requires incident UUID and title, with optional status.

Instructions

特定のインシデントに新しいアクションアイテムを作成します。

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": {
      "incident_uuid": "<incident_uuid>",
      "title": "<title>"
    },
    "name": "waroom_create_incident_action_item"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	アクションアイテムのタイトル
`status`	No	アクションアイテムのステータス。デフォルト: open
`incident_uuid`	Yes	インシデントのUUID

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.0Jul 22, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, description carries full burden but only states 'creates'. No disclosure of side effects, permissions needed, or return behavior. Minimal transparency.

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?

Single sentence is concise and efficient. No redundant information. Could be slightly more informative without losing conciseness.

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 tool with 3 parameters and no output schema, description is insufficient. Missing return format, error cases, or effects on incident.

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 coverage is 100%, so baseline 3 applies. Description adds no extra meaning beyond existing parameter descriptions in schema.

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?

Description clearly states 'creates a new action item for a specific incident' with specific verb and resource. Distinguishes from sibling tools by focusing on creating action items.

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_update_incident_action_item or waroom_get_incident_action_items. No prerequisites or context provided.

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