Skip to main content
Glama

pve_ceph_osd_lv_info

Retrieves LVM logical volume details (size, path, UUID, VG) for a Ceph OSD's block, DB, or WAL device on a Proxmox node.

Instructions

READ-ONLY: an OSD's logical-volume details (LVM-reported via lvs, on the SAME host administering this OSD). REVIEWED_TRUSTED (argued, not asserted — see ceph.py module docstring's Taint section): closed schema shape (no additionalProperties:1), local-host command output rather than a remote/cluster daemon self-report at registration.

GET /nodes/{node}/ceph/osd/{osdid}/lv-info[?type=]. Smoke-confirm: shape not live-verified — expected {creation_time, lv_name, lv_path, lv_size, lv_uuid, vg_name} per schema truth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node name to query; defaults to the configured node if omitted.
osdidYesOSD ID (0 is a valid id — the first OSD ever created).
lv_typeNoOSD device type to inspect: 'block' (default), 'db', or 'wal'. Named to avoid shadowing the `type` builtin — the wire query param is still the schema's literal `type`.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Clearly states read-only nature upfront, mentions REVIEWED_TRUSTED and closed schema shape, spells out data source (LVM via lvs), and notes that shape is not live-verified. Fully discloses operational traits without annotations.

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 'READ-ONLY' and efficient explanation. Every sentence provides value, though slightly verbose with technical asides. Still concise given complexity.

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

Completeness5/5

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

Comprehensive: explains what, where, expected output fields, and verification state. Output schema exists, so return value coverage is adequate. Fully equips agent to understand the tool's role.

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 has 100% description coverage with detailed parameter docs, so description does not need to add much. Baseline 3 is appropriate; description adds no extra parameter-level value.

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?

The description explicitly states it is 'READ-ONLY' for querying LVM-reported logical-volume details of an OSD on the same host. It distinguishes from sibling tools by emphasizing local-host command output vs remote/cluster daemon self-report.

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

Usage Guidelines4/5

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

Implies usage for local LVM details and contrasts with remote/cluster alternatives. Provides context about scope (same host, local command). Lacks explicit when-not-to-use but sufficiently guides selection among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server