Lists Docker Swarm tasks with their state and node, optionally filtered by service or agent, to help monitor running service units.
List Docker Swarm tasks (the running units of a service), optionally filtered by service, with their state and node.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | No | Filter by agent UUID, or 'local'. Omit for all. | |
| service_id | No | Filter by service ID. Omit for all tasks. |
Changes observed during successful MCP inspections.
v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context by defining tasks and noting that state and node are included, but it does not cover pagination, response shape, or any access constraints.
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?
It is a single efficient sentence with the core action front-loaded and a useful parenthetical definition. Every clause contributes to understanding the tool.
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?
For a simple list tool with only two optional parameters, full schema coverage, and a readOnly annotation, this is mostly complete. It also mentions the returned state and node, though it could note pagination or ordering behavior.
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?
Schema description coverage is 100%, so both parameters are already well documented in the schema. The description only echoes the service filter and does not mention the agent_id filter, so it adds little beyond the schema.
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 ('List Docker Swarm tasks') and clarifies that tasks are the running units of a service, including returned state and node. It is clear on its own, but it does not explicitly distinguish itself from nearby siblings like list_swarm_services or get_swarm_info.
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?
It says tasks can be optionally filtered by service and that omission returns all tasks, which gives implied usage. However, it does not explain when to use this tool instead of list_swarm_services, list_swarm_nodes, or get_swarm_info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.