Skip to main content
Glama
Sign In
rrdmcp

rrdmcp

by wtnb75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_hosts

Retrieve all group-host pairs discovered from Munin datafiles to see which hosts and groups are available for metric queries.

Instructions

List all (group, host) pairs discovered from the Munin datafile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. 'List all' signals a read-only, exhaustive enumeration, and 'discovered from the Munin datafile' clarifies the data source. It does not mention caveats like missing datafiles or performance, but the read-only nature is clear.

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?

The description is a single, front-loaded sentence with no redundant wording. Every word adds information: the operation, the output shape, and the data source.

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?

This is a simple parameterless enumeration tool with an output schema available. The description names the exact result and source, which is sufficient for an agent to select and invoke it correctly. No additional prerequisites or alternatives are necessary for this straightforward operation.

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 has zero parameters and the schema is empty, so there is no parameter detail for the description to add. The description appropriately focuses on what the tool returns rather than arguments.

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?

The description clearly identifies the action ('List'), the resource ('(group, host) pairs'), and the data source ('Munin datafile'). It differentiates from siblings like list_plugins and list_fields by naming the specific pair type, though it does not explicitly call out the distinction.

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 usage context is implied: use this tool when you need all discovered group-host pairs from the Munin datafile. However, it provides no explicit guidance about when not to use it or which sibling tool to prefer for other listing needs.

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