Skip to main content
Glama

Get Ceph OSD flags

proxmox_get_ceph_flags
Read-only

Retrieve which cluster-wide Ceph OSD flags are currently set, such as noout, noscrub, nodeep-scrub, norebalance, or pause, to check cluster maintenance state.

Instructions

Show which cluster-wide Ceph OSD flags are set (noout, noscrub, nodeep-scrub, norebalance, pause...). Change them with proxmox_set_ceph_flags.

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": "proxmox_get_ceph_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is established. The description adds useful scope information (cluster-wide rather than per-OSD) and example flag names, but says nothing about the return shape (e.g., a list of set flags vs. a full flag/state map) or whether all OSDs are covered.

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?

Two short sentences, front-loaded with the operation and resource, followed by the sibling hand-off. No filler, no repetition of the title.

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 zero-arg read tool with annotations covering the safety hints, the description is nearly sufficient. The one remaining gap is that no output schema exists, so the agent must infer the response shape from "which flags are set" alone.

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

Parameters4/5

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

The schema has zero properties, which is the baseline-4 case. The description appropriately adds no fabricated parameter detail and instead spends its words on scope and output expectations.

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 ("Show") and a precisely scoped resource ("cluster-wide Ceph OSD flags"), then names the concrete flags returned (noout, noscrub, nodeep-scrub, norebalance, pause). This is clearly distinguishable from sibling getters like proxmox_get_ceph_status or proxmox_get_ceph_config.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent in both directions: this tool to inspect, and proxmox_set_ceph_flags to change them. For a zero-parameter read tool, that pairing covers the only meaningful decision the caller has to make.

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

Deploy Server

Other Tools