io.github.AIops-tools/ceph-aiops

pool_create

Destructive

Create a replicated Ceph storage pool by setting its name, placement-group count, replica size, and application tag for RBD, CephFS, or RGW workloads.

Instructions

[WRITE][risk=medium] Create a replicated pool.

Args: pool_name: Name for the new pool. pg_num: Initial placement-group count (default 32). size: Replica count (default 3). application: Pool application tag: "rbd", "cephfs", or "rgw" (default "rbd"). target: Ceph target name from config; omit for the default.

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": {
      "pool_name": "<pool_name>"
    },
    "name": "pool_create"
  }
}

Input Schema

Name	Required	Default
`size`	No
`pg_num`	No
`target`	No
`pool_name`	Yes
`application`	No	rbd

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the '[WRITE]' tag is largely redundant. The description does add the 'risk=medium' severity rating and implicitly confirms the non-idempotent create semantics, but it says nothing about failure behavior when the pool already exists, cluster-side side effects, or whether the call blocks.

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?

Front-loaded with the write/risk signal, then a tight per-argument list. The defaults (32, 3, "rbd") duplicate what the schema already declares, which is minor waste, but the rest of the text earns its place.

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

Completeness4/5

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

For a five-parameter mutation tool with no output schema, the description covers what is being created and all inputs, and annotations carry the destructive/non-idempotent profile. It stops short of stating prerequisites (cluster reachability, auth level) or what happens on a name collision, which an agent provisioning into an existing cluster would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden — and it does: every one of the five parameters is explained, including the enum values for 'application' ("rbd", "cephfs", "rgw") that are absent from the schema, plus the meaning of 'target' as a config-sourced Ceph target name.

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?

States a specific verb and resource — 'Create a replicated pool' — which an agent can immediately distinguish from pool_delete, pool_ls, and pool_df. The '[WRITE][risk=medium]' prefix reinforces the operation type up front.

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?

There is no guidance on when to use this tool versus alternatives such as rbd_image_create (which may implicitly create a pool) or the pool_* mutation siblings like set_pool_size. No prerequisites, permissions, or environment conditions are mentioned; the agent must infer that this is the initial pool-provisioning step.

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