freebox-mcp

by Nelson-PROIA

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

put_storage_disk_id

Enable or disable a disk on Freebox storage, handling errors for invalid, partition, internal, or busy disks.

Instructions

Enable/Disable a disk

Error codes: not_found, invalid_disk, is_a_partition, is_internal, op_not_supported, op_failed, disk_busy

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`body`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Jun 21, 2026
- changedInput schema / properties / id / type
```
Previous value: -"integer"New value: +"string"
```

Changed20 schema fields changedJun 21, 2026

removedInput schema / properties / active_duration

Removed value: -{
-  "description": "disk activity duration (in seconds) (when available)",
-  "type": "integer"
-}

addedInput schema / properties / body

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

removedInput schema / properties / connector

Removed value: -{
-  "description": "Disk physical connector id",
-  "type": "integer"
-}

removedInput schema / properties / firmware

Removed value: -{
-  "description": "Disk firmware version",
-  "type": "string"
-}

removedInput schema / properties / id / description
```
Removed value: -"the disk id"
```

removedInput schema / properties / id__path

Removed value: -{
-  "description": "the disk id to enable/disable (Path parameter)",
-  "type": "integer"
-}

removedInput schema / properties / idle

Removed value: -{
-  "description": "is disk idle (when available)",
-  "type": "boolean"
-}

removedInput schema / properties / idle_duration

Removed value: -{
-  "description": "disk idle duration (in seconds) (when available)",
-  "type": "integer"
-}

removedInput schema / properties / model

Removed value: -{
-  "description": "Disk model",
-  "type": "string"
-}

removedInput schema / properties / operation_pct

Removed value: -{
-  "description": "partition operation progress",
-  "properties": {
-    "done_steps": {
-      "description": "number of steps done",
-      "type": "integer"
-    },
-    "max_steps": {
-      "description": "total number of steps",
-      "type": "integer"
-    },
-    "percent": {
-      "description": "current step progress",
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}

removedInput schema / properties / partitions

Removed value: -{
-  "description": "list of disk partitions",
-  "items": {
-    "description": "Disk partitions have the following attributes:",
-    "properties": {
-      "disk_id": {
-        "description": "related disk id",
-        "type": "integer"
-      },
-      "free_bytes": {
-        "description": "partition free space (in bytes)",
-        "type": "integer"
-      },
-      "fsck_result": {
-        "description": "fsck result — Values: `no_run_yet`: Partition has not been checked yet; `running`: Check is in progress; `fs_clean`: File system is ok; `fs_corrected`: File system was corrected; `fs_needs_correction`: File system need correction; `failed`: File system has unrecoverable error",
-        "enum": [
-          "no_run_yet",
-          "running",
-          "fs_clean",
-          "fs_corrected",
-          "fs_needs_correction",
-          "failed"
-        ],
-        "type": "string"
-      },
-      "fstype": {
-        "enum": [
-          "empty",
-          "unknown",
-          "xfs",
-          "ext4",
-          "vfat",
-          "ntf",
-          "hf",
-          "hfsplus",
-          "swap",
-          "exfat"
-        ],
-        "type": "string"
-      },
-      "id": {
-        "description": "unique partition id",
-        "type": "integer"
-      },
-      "label": {
-        "description": "partition name",
-        "type": "string"
-      },
-      "operation_pct": {
-        "description": "partition operation progress",
-        "properties": {
-          "done_steps": {
-            "description": "number of steps done",
-            "type": "integer"
-          },
-          "max_steps": {
-            "description": "total number of steps",
-            "type": "integer"
-          },
-          "percent": {
-            "description": "current step progress",
-            "type": "integer"
-          }
-        },
-        "type": "object"
-      },
-      "path": {
-        "description": "partition mount point (encoded in base64 as explained in fs API)",
-        "type": "string"
-      },
-      "state": {
-        "description": "Values: `error`: Partition has error; `checking`: Partition check in progress; `formatting`: Partition format in progress; `mounting`: Partition mount in progress; `maintenance`: Partition is in maintenance mode; `mounted`: Partition is ready; `umounting`: Partition umount in progress; `umounted`: Partition is umounted; `ejecting`: Partition ejection in progress",
-        "enum": [
-          "error",
-          "checking",
-          "formatting",
-          "mounting",
-          "maintenance",
-          "mounted",
-          "umounting",
-          "umounted",
-          "ejecting"
-        ],
-        "type": "string"
-      },
-      "total_bytes": {
-        "description": "partition size (in bytes)",
-        "type": "integer"
-      },
-      "used_bytes": {
-        "description": "partition used space (in bytes)",
-        "type": "integer"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedInput schema / properties / serial

Removed value: -{
-  "description": "Disk serial number",
-  "type": "string"
-}

removedInput schema / properties / spinning

Removed value: -{
-  "description": "is disk spinning (when available)",
-  "type": "boolean"
-}

removedInput schema / properties / state

Removed value: -{
-  "description": "Values: `error`: Disk has error; `disabled`: Disk is disabled; `enabled`: Disk is enabled; `formatting`: Disk is formatting",
-  "enum": [
-    "error",
-    "disabled",
-    "enabled",
-    "formatting"
-  ],
-  "type": "string"
-}

removedInput schema / properties / table_type

Removed value: -{
-  "enum": [
-    "msdos",
-    "gpt",
-    "superfloppy",
-    "empty"
-  ],
-  "type": "integer"
-}

removedInput schema / properties / temp

Removed value: -{
-  "description": "Disk temperature (when supported) in °C",
-  "type": "integer"
-}

removedInput schema / properties / time_before_spindown

Removed value: -{
-  "description": "seconds left before disk spin down (in seconds) (when available)",
-  "type": "integer"
-}

removedInput schema / properties / total_bytes

Removed value: -{
-  "description": "Disk size (in bytes)",
-  "type": "integer"
-}

removedInput schema / properties / type

Removed value: -{
-  "description": "Values: `internal`: Freebox internal disk; `usb`: usb disk; `sata`: sata disk",
-  "enum": [
-    "internal",
-    "usb",
-    "sata"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "id__path"
-]New value: +[
+  "id"
+]

First observedv0.1.0Jun 21, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action and lists error codes, but does not disclose side effects, permissions, or what the 'body' parameter does.

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?

The description is short but includes error codes, which is useful. However, it lacks structure and could better organize information.

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?

Given the tool's complexity (mutation, free-form body) and lack of output schema details, the description is insufficient for an agent to safely invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. While 'id' is self-explanatory, the 'body' parameter is an object with 'additionalProperties: true', and the description gives no hint about expected keys or structure.

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 states the tool's action as 'Enable/Disable a disk', specifying the verb and resource. It is distinguishable from siblings like 'put_storage_disk_id_format' which is for formatting.

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 guidance on when to use this tool versus alternatives. Error codes hint at conditions but do not provide explicit usage context or prerequisites.

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

Install Server