Skip to main content
Glama

Get Ceph configuration

proxmox_get_ceph_config
Read-only

Read Ceph configuration from the config database and/or ceph.conf to review cluster settings, with secret keys redacted. Filter by source or search term.

Instructions

Read Ceph configuration: the configuration database (ceph config dump: section, name, value) and/or the ceph.conf file. Secrets such as keys are redacted.

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_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
sourceNoConfiguration database, ceph.conf file, or both (default both)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds real value by disclosing that secrets such as keys are redacted — a behavior an agent could not infer from the schema. It also names the underlying API call and its returned fields, aiding interpretation. Minor gap: it doesn't explain why idempotentHint=false on what reads like a repeatable read.

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?

A single front-loaded sentence naming the resource and both sources, plus one short sentence carrying the important redaction caveat. No filler, no redundancy with 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 read-only, zero-required-parameter tool with fully documented schema and no output schema, this is close to complete: purpose, sources, and the secret-redaction caveat are all present. The only shortfall is the absence of any note on output shape or how the two sources are combined when 'both' is selected.

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 all three parameters (node, search, source) are already documented in the schema, including the enum for source and the default-node fallback. The description adds only the mapping of 'database' to `ceph config dump` fields; it doesn't clarify how search interacts with each source or what 'Results are cluster-wide' means per-source.

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?

States a specific verb ('Read') and resource ('Ceph configuration'), and scopes it precisely to two data sources: the config database via `ceph config dump` (section, name, value) and the ceph.conf file. That scope naturally separates it from siblings such as proxmox_get_ceph_status, proxmox_get_ceph_flags, or proxmox_get_ceph_pool, though the description never explicitly contrasts with them.

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

Usage Guidelines3/5

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

The phrase 'and/or' implies the caller can choose a source, and the tool's purpose is clear, but there is no explicit when-to-use guidance, no stated prerequisites (e.g., Ceph installed), and no named alternative for configuration-adjacent tasks like flags or CRUSH maps. Usage is implied rather than directed.

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