Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Bill History Graph Data

bill_history_graph_data
Read-onlyIdempotent

Retrieve historical billing graph data for a LibreNMS bill by bill ID, history ID, and graph type to analyze traffic or transfer rates.

Instructions

Get bill history graph data from LibreNMS.

Input Schema

NameRequiredDescriptionDefault
bill_idYesBill ID
graph_typeYesGraph type for a past billing period: 'bits' (traffic), 'day' or 'hour' (transfer per day or hour)
history_idYesBill history ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.12.0
    • changedInput schema / properties / graph_type / description
      Previous value: -"Graph type: bits, monthly, hour, or day"New value: +"Graph type for a past billing period: 'bits' (traffic), 'day' or 'hour' (transfer per day or hour)"
    • addedInput schema / properties / graph_type / enum
      Added value: +[
+  "bits",
+  "day",
+  "hour"
+]
  2. First observedv1.9.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond those annotations—no auth requirements, rate limits, or return characteristics—and does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no wasted words, so it is concise. However, it is under-specified rather than informative—the sentence essentially restates the name and contributes little.

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

Completeness2/5

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

With three required parameters and several similarly named siblings, the description provides no scope distinction or routing information. The output schema covers return values, but the selection context an agent needs is missing.

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%, with clear parameter documentation including an explanatory enum for graph_type ('bits', 'day', 'hour'). The description adds no parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title ('Get bill history graph data') and adds only 'from LibreNMS,' which is system context rather than a distinguishing purpose. It does not differentiate from near-identical siblings such as bill_graph_data, bill_history_graph, or bill_graph.

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?

No when-to-use guidance, prerequisites, or alternatives are provided. Given the sibling set contains confusingly similar names (bill_graph, bill_graph_data, bill_history_graph), the absence of any routing hint leaves the agent without guidance.

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