Skip to main content
Glama

generate_collection_skills

Idempotent

Batch generate skills for an entire Ansible collection. Updates MANIFEST.json and AGENTS.md so agents can discover and use the collection's modules and plugins.

Instructions

Batch generate skills for an entire collection.

Generates/updates the collection MANIFEST.json as a byproduct. Updates AGENTS.md in the project root with a managed section listing available collections for cross-agent discovery. Returns {"succeeded": int, "failed": int, "total": int, "manifest": dict, "collection_skill": str}, or {"error": str} on failure.

Module/plugin docs use batched ansible-doc calls. Names missing from a batch (or a hard batch failure) are counted in failed; partial batch success still writes skills for resolved names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
install_toNoOptional absolute path to install skills to. Defaults to the project skills/ directory (via ANSIBLE_KNOW_SKILLS_DIR, or ANSIBLE_KNOW_PROJECT_DIR/CLAUDE_PROJECT_DIR/cwd + /skills).
collection_namespaceYesCollection namespace (e.g. 'netbox.netbox')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the idempotentHint annotation, the description reveals significant side effects: it updates MANIFEST.json and AGENTS.md. It also discloses the return shape, including an error variant, and explains partial-batch success behavior (missing names counted as failed, but resolved names still written). This is rich, honest behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately long but well-structured into a lead sentence, a side-effect paragraph, a return-value paragraph, and a behavior note. Every sentence adds value, with key information front-loaded. Slightly verbose but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, the description covers purpose, side effects, return values, and failure semantics. The output schema exists, yet the description still summarizes the return type and error case, making it self-sufficient. No significant gaps identified.

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

Parameters3/5

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

Schema description coverage is 100%: both parameters (install_to and collection_namespace) have detailed descriptions in the schema. The tool description itself adds no additional parameter semantics, so it stays at the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Batch generate skills for an entire collection.' This clearly distinguishes it from sibling tools like generate_skill and generate_plugin_skill by emphasizing the collection-wide scope. It also states the byproducts (MANIFEST.json and AGENTS.md updates) further clarifying its unique role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use this tool: for batch skill generation across a collection, with mention of batched ansible-doc calls. However, it does not explicitly say 'use this instead of generate_skill' or list alternatives/exclusions. Context is strong but explicit guidance against alternatives is missing.

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/leogallego/ansible-know-mcp'

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