Skip to main content
Glama

put_storage_disk_id_format

Format a disk by ID, erasing all data and creating a single partition using the full disk space. Monitor progress via the disk's operation_pct field.

Instructions

Format the disk with the given id To be able to format a disk you need to provide the following parameters (JSON encoded). There will be one partition using all the available space on disk. All previous data will be lost. This parameters will be ignored if you format the Freebox internal disk NOTE: once started you can monitor the format process getting the disk information (see StorageDisk operation_pct field)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNothe disk id
typeNoValues: `internal`: Freebox internal disk; `usb`: usb disk; `sata`: sata disk
stateNoValues: `error`: Disk has error; `disabled`: Disk is disabled; `enabled`: Disk is enabled; `formatting`: Disk is formatting
connectorNoDisk physical connector id
total_bytesNoDisk size (in bytes)
table_typeNo
modelNoDisk model
serialNoDisk serial number
firmwareNoDisk firmware version
tempNoDisk temperature (when supported) in °C
operation_pctNopartition operation progress
partitionsNolist of disk partitions
idleNois disk idle (when available)
idle_durationNodisk idle duration (in seconds) (when available)
spinningNois disk spinning (when available)
active_durationNodisk activity duration (in seconds) (when available)
time_before_spindownNoseconds left before disk spin down (in seconds) (when available)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It effectively discloses that all previous data will be lost, that monitoring is possible via the operation_pct field, and lists relevant error codes. This provides a clear behavioral picture for an irreversible operation.

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 somewhat run-on and could be better organized into sentences or bullet points. It includes all essential information but is not optimally concise or structured.

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?

Given the presence of an output schema, the description covers the key workflow (format, monitor, error codes). It lacks details on prerequisites (e.g., disk state before formatting) but is largely complete for the tool's purpose.

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

Parameters4/5

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

Schema coverage is high (94%), so baseline is 3. The description adds valuable context: parameter encoding (JSON) and the fact that parameters are ignored for internal disks. This goes beyond the schema's own descriptions.

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 'Format the disk with the given id' and explains that it creates a single partition and data is lost. However, it does not explicitly differentiate from sibling tools like put_storage_disk_id or put_storage_partition_id, leaving some ambiguity about when to use this specific tool.

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?

The description lacks guidance on when to use this tool versus alternatives. It mentions prerequisites ('provide the following parameters') but does not specify when formatting is appropriate or when other storage tools should be used, leaving the agent without explicit decision-making cues.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server