Waroom MCP

waroom_get_runbooks

Retrieve a paginated list of runbooks. Specify page and per_page to control which results are returned.

Instructions

ランブックの一覧を取得します。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "waroom_get_runbooks"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	取得するページ番号（1以上の整数）。デフォルト: 1
`per_page`	No	1ページあたりの取得数（1-100）。デフォルト: 50

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.0Jul 22, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It only states 'Get a list of runbooks' without any mention of pagination, ordering, rate limits, or side effects. This leaves the agent unaware of how results are returned or any constraints.

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 very concise at one sentence, which is efficient. However, the brevity sacrifices important behavioral details. Front-loading is good as the purpose is stated upfront. It could be slightly expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with two basic parameters (page, per_page) and no output schema, the description is somewhat complete but lacks context about what a runbook is or the structure of the returned list. It meets minimum viability but leaves room for improvement.

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?

The input schema already describes both parameters (page, per_page) with clear descriptions in Japanese. The tool description adds no additional meaning beyond what the schema provides. Since schema coverage is 100%, baseline score of 3 is appropriate.

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 the action (get/list) and resource (runbooks) in Japanese. It uses a specific verb '取得する' and identifies the resource as 'ランブックの一覧', making the purpose unambiguous. It also distinguishes from sibling tool 'waroom_get_runbook' which retrieves a single runbook.

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_get_runbook' (single) or 'waroom_get_runbooks' (this one). There is no mention of prerequisites, filters, or scenarios where using this tool is inappropriate.

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