Skip to main content
Glama
mhajder

librenms-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Bill History Graph

bill_history_graph
Read-onlyIdempotent

Render a graph for a past billing period as an image using bill ID, history ID, and graph type. Use it to visualize historical traffic or transfer.

Instructions

Render a graph for a past billing period as an image.

For the underlying numbers rather than a picture, use bill_history_graph_data.

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

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. Changed1 schema field changedv1.11.1
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. First observedv1.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuinely useful behavioral context by disclosing that the response is an image rather than structured data — critical information with no output schema. It omits image format and any size/pagination notes.

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?

Two short sentences, zero filler, with the primary capability front-loaded and the alternative-tool hint immediately after. Every sentence earns its place.

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 three-required-parameter read tool with full schema coverage and no output schema, the description supplies the missing piece — that the return is an image. It stops short of describing format or how the image is delivered, which would complete the picture.

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 coverage is 100%, and the schema itself documents bill_id, history_id, and the graph_type enum values with their meanings. The description adds no parameter detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb (render), resource (graph for a past billing period), and output form (image) in one sentence. It clearly separates itself from bill_history_graph_data and the other graph siblings by declaring it returns a picture, not numbers.

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?

Explicitly routes the agent to bill_history_graph_data when the underlying numbers are wanted instead of a picture, which is the key decision point between the two siblings. It does not, however, clarify the boundary against bill_graph/bill_graph_data (current vs past period).

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