dpanel_container_exportExports a Docker container as an image tar file, letting you save and transfer container state for backup or migration. Requires the container MD5 identifier.
导出容器为镜像 tar。
| Name | Required | Description | Default |
|---|---|---|---|
| md5 | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it only says the output is an image tar. It does not state whether the operation is read-only or writes to disk, where the tar is saved, permission requirements, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one short, front-loaded sentence with no wasted words. However, it is arguably too terse for a tool with an undocumented parameter, missing essential context that would make the brevity appropriately sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. But the description fails to cover the critical 'md5' parameter and provides no usage context, leaving significant gaps for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single required parameter 'md5' has 0% schema description coverage and is not mentioned in the description at all. The agent cannot know what value to supply for 'md5', making correct invocation impossible without guesswork.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'export container as image tar'. This is clear and distinguishable from generic container operations, though it does not explicitly differentiate from siblings like dpanel_container_commit or dpanel_container_backup_create that also produce artifacts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as dpanel_container_commit or dpanel_container_backup_create. The description only states what it does, leaving the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.