Skip to main content
Glama
Nelson-PROIA

freebox-mcp

by Nelson-PROIA
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

post_rrd

Export Freebox RRD data to analyze network performance and usage trends over time.

Instructions

post_rrd

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / date_end
      Removed value: -{
-  "description": "The requested end timestamp of the stats to get",
-  "type": "integer"
-}
    • removedInput schema / properties / date_start
      Removed value: -{
-  "description": "The requested start timestamp of the stats to get",
-  "type": "integer"
-}
    • removedInput schema / properties / db
      Removed value: -{
-  "description": "Name of the rrd database to read. It can take one of the following values — Values: `net`: network stats; `temp`: temperature stats; `dsl`: xDSL stats; `switch`: switch stats",
-  "enum": [
-    "net",
-    "temp",
-    "dsl",
-    "switch"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / fields
      Removed value: -{
-  "description": "If you are only interested in getting some fields you can provide the list of fields you want to get.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / precision
      Removed value: -{
-  "description": "By default all values are cast to int, if you need floating point precision you can provide a precision factor that will be applied to all values before being returned.",
-  "type": "integer"
-}
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.1.0

TDQS

D1.4/5.0
Behavior1/5

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

No annotations provided, and the description gives no behavioral information (e.g., side effects, required permissions, or response format). For a mutation tool, this is a critical omission.

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

Conciseness2/5

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

Extremely concise (one word) but at the cost of meaningful information. This is underspecification, not efficient clarity.

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

Completeness1/5

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

Completely inadequate. Despite zero parameters, the tool's purpose and behavior are entirely opaque, especially given the existence of a sibling 'get_rrd' tool.

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?

The input schema has no parameters, so schema coverage is 100%. Baseline is 3, and the description adds nothing beyond the schema.

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

Purpose1/5

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

Tautological: description restates name/title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., 'get_rrd' for reading). Description provides no context for invocation.

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

Install Server

Other Tools