Skip to main content
Glama

node_status

Read-onlyIdempotent

Retrieve the status of the configured Proxmox node to check its health and resource state without making infrastructure changes.

Instructions

Read status of the configured node; no infrastructure modifications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's 'no infrastructure modifications' largely restates that, adding only the useful detail that the tool operates on the already-configured node rather than an arbitrary target. It says nothing about what status data is returned or freshness.

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?

A single short sentence with the action front-loaded and the safety qualifier trailing. It is tight, though the second clause partly duplicates what the annotations already state, so it earns slightly less than full marks.

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-parameter, read-only status tool with rich annotations and no output schema, the description covers what an agent needs to call it correctly: the target is implicit and the call is non-mutating. Readers are left without any hint of what the returned status contains, a minor gap given the absent output schema.

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 tool takes zero parameters, which sets the baseline at 4. The phrase 'the configured node' usefully explains why no target parameter exists — the node is determined by configuration rather than input.

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 status of the configured node'. An agent can tell this is a node-scoped read, distinct from siblings like storage_status or backup_history, though the description does not explicitly name or contrast any of 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?

Usage is only implied: 'the configured node' tells the agent no target selection is needed, and 'no infrastructure modifications' signals a safe inspection call. There is no explicit when-to-use condition, prerequisite, or named alternative, so the agent must infer when node status is the right check versus storage_status or list_guests.

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