Collections vs requirements
ansible_collectionsCheck requirements.yml against installed Ansible collections and roles, reporting OK, VIOLATES with file:line, or MISSING items and shadowed collection paths; never installs anything.
Instructions
requirements.yml (collections and roles) against what is installed: ok, VIOLATES (with file:line) or MISSING, using galaxy constraint rules, plus collections shadowed across collections paths (the first in COLLECTIONS_PATHS wins). Never installs anything.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ansible_collections"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dir | No | Ansible project directory. Default: ANSIBLE_MCP_DIR, else the server's working directory. | |
| requirements | No | Requirements file relative to dir (default: requirements.yml, collections/requirements.yml, roles/requirements.yml) | |
| include_extras | No | List installed collections nothing requires |