Skip to main content
Glama
Nelson-PROIA

freebox-mcp

by Nelson-PROIA
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

put_storage_partition_id

Enable or disable a storage partition on your Freebox Server. Use this tool to manage partition availability.

Instructions

Enable/Disable a partition

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
bodyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / id / type
      Previous value: -"integer"New value: +"string"
  2. Changed14 schema fields changed
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • removedInput schema / properties / disk_id
      Removed value: -{
-  "description": "related disk id",
-  "type": "integer"
-}
    • removedInput schema / properties / free_bytes
      Removed value: -{
-  "description": "partition free space (in bytes)",
-  "type": "integer"
-}
    • removedInput schema / properties / fsck_result
      Removed value: -{
-  "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"
-}
    • removedInput schema / properties / fstype
      Removed value: -{
-  "enum": [
-    "empty",
-    "unknown",
-    "xfs",
-    "ext4",
-    "vfat",
-    "ntf",
-    "hf",
-    "hfsplus",
-    "swap",
-    "exfat"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / id / description
      Removed value: -"unique partition id"
    • removedInput schema / properties / id__path
      Removed value: -{
-  "description": "the partition id to enable/disable (Path parameter)",
-  "type": "integer"
-}
    • removedInput schema / properties / label
      Removed value: -{
-  "description": "partition name",
-  "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 / path
      Removed value: -{
-  "description": "partition mount point (encoded in base64 as explained in fs API)",
-  "type": "string"
-}
    • removedInput schema / properties / state
      Removed value: -{
-  "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"
-}
    • removedInput schema / properties / total_bytes
      Removed value: -{
-  "description": "partition size (in bytes)",
-  "type": "integer"
-}
    • removedInput schema / properties / used_bytes
      Removed value: -{
-  "description": "partition used space (in bytes)",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "id__path"
-]New value: +[
+  "id"
+]
  3. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It lists error codes, which is helpful. However, it does not disclose side effects (e.g., data loss, unmounting requirements) or permissions needed. The mutation nature is implied but not detailed.

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 very short (one phrase plus error codes). It is concise but lacks structure and front-loading. The error codes are listed, but the main action is not elaborated. Could be improved with a brief sentence on behavior.

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?

For a mutation tool with output schema, the description fails to clarify success/failure response or state changes. No mention of relationship to get_storage_partition_id or other storage tools. Error codes partially compensate, but overall incomplete.

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%, and the description does not explain the parameters at all. The 'id' is clear from the name, but the 'body' parameter (additionalProperties: true) is completely unspecified. The agent has no guidance on what properties to include (e.g., enabled).

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 'Enable/Disable a partition', specifying the verb and resource. The tool name and sibling tools confirm it operates on a specific partition by ID. However, it could be more precise about what 'enable/disable' means (e.g., mounting state).

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 like put_storage_partition_id_check. No prerequisites (e.g., disk must be present) or exclusions provided. The description lacks any usage context.

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