Skip to main content
Glama

Read Ceph log

proxmox_get_ceph_log
Read-only

Read Ceph cluster log lines from a Proxmox node to inspect health changes, OSD up/down events, slow ops, and scrub errors; filter by search term and paginate results.

Instructions

Read lines of the Ceph cluster log (ceph.log) from a node: health changes, OSD up/down events, slow ops and scrub errors.

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

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.
limitNoNumber of lines (default 50)
startNoOffset of the first line (0-based)
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety and mutability are covered. The description adds the concrete artifact being read (ceph.log) and its event classes, but says nothing about ordering, truncation, or how limit/start interact when the log is large — useful context for a non-idempotent 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 verb, the resource, the file, and the content classes, with no filler. Nothing could be removed without losing information.

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 log reader with a fully documented 4-parameter schema and no output schema, the definition covers what is being read and where it comes from. It is only slightly thin on how paging over a large log behaves, which matters given the 5000-line cap.

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 description coverage is 100%, so node, limit, start and search are all already documented, including the cluster-wide caveat on node. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource: read lines of the Ceph cluster log (ceph.log) from a node, and enumerates what it contains (health changes, OSD up/down, slow ops, scrub errors). The naming of the concrete file distinguishes it in practice from sibling log readers like proxmox_get_cluster_log or proxmox_get_task_log, though no sibling is named explicitly.

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?

The list of log content types hints at diagnostic use, but there is no explicit when-to-use statement, no exclusions, and no pointer to alternatives such as proxmox_get_ceph_status for current state versus log history. The agent must infer why it would pick this log over the other log tools.

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