Lists hosts from an Ansible inventory file. Provide the inventory path to retrieve the managed hosts defined in it.
List inventory hosts.
| Name | Required | Description | Default |
|---|---|---|---|
| inventory | Yes | Inventory path |
Changes observed during successful MCP inspections.
v1.0.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. 'List' weakly implies a read-only operation, but the description does not state whether it has side effects, requires special permissions, or how it behaves if the inventory path is invalid.
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 a single, front-loaded sentence with no filler. It is appropriately sized for a very simple tool with one parameter.
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 one-parameter list operation, the description is minimally adequate, but it lacks important context such as what the output looks like, error behavior, and whether the inventory path should be a file or directory. These gaps matter more because there is no output schema or annotations.
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 schema already provides 100% coverage by describing the only parameter as 'Inventory path'. The description adds no additional meaning about the parameter, so the baseline score of 3 is appropriate.
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 uses a specific verb ('List') and resource ('inventory hosts'), and the operation is clearly distinct from sibling tools like ansible_run_playbook and ansible_syntax_check. It stops short of a 5 because it does not explicitly differentiate itself or clarify the exact kind of inventory listing (e.g., hostnames only versus full inventory details).
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?
The description gives no guidance on when to use this tool versus the sibling tools. It does not mention typical use cases, exclusions, or alternatives such as ansible_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.