Skip to main content
Glama

package_as_plugin

DestructiveIdempotent

Wrap generated Ansible skills into an Agent Plugins directory with plugin.json and optional mcp.json, replacing existing skills trees to produce a distributable plugin archive.

Instructions

Wrap already-generated skills into an Agent Plugins directory.

Does not change generate_* output layout. Copies skills/{collection-kebab}/{skill}/ into {output_dir}/{plugin}/skills/{skill}/ and writes plugin.json (and optionally mcp.json + .tar.gz) per the Agent Plugins specification. Replaces any existing skills/ tree under the target plugin directory (destructive but idempotent).

Returns: {"collection", "plugin_name", "plugin_dir", "skill_count", "skills", "plugin_json", "mcp_json", "archive"} or {"error": str} on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcp_urlNoAbsolute MCP endpoint URL when mcp_transport is 'streamable-http' (e.g. 'https://aap.example.com/mcp/skills/'). Ignored for stdio.
collectionYesCollection namespace whose generated skills to wrap (e.g. 'netbox.netbox').
output_dirYesParent directory where the Agent Plugin directory will be created (e.g. '.' or '/tmp/agent-plugins').
source_dirNoOptional skills root to read from. Defaults to ANSIBLE_KNOW_SKILLS_PATH or SKILLS_DIR (same roots as list_skills).
plugin_nameNoOptional Agent Plugins manifest name / directory name. Defaults to 'ansible-{collection-kebab}-agentplugin' (e.g. 'ansible-netbox-netbox-agentplugin'). Must satisfy Agent Plugins §5.5 (1-64 chars, [a-z0-9.-]).
mcp_transportNoMCP transport for mcp.json when include_mcp_config is true: 'stdio' (default, uvx ansible-know-mcp) or 'streamable-http' (requires mcp_url for an AAP-hosted know-mcp endpoint).stdio
write_tarballNoWhen true (default), also write {plugin_name}-{version}.tar.gz beside the plugin directory (Pulp/AAP-friendly artifact). Requires write_plugin_json=True.
write_plugin_jsonNoWhen true (default), write plugin.json with Agent Plugins v1.0.0 manifest fields. Required when write_tarball is true.
include_mcp_configNoWhen true (default), write mcp.json for know-mcp (see mcp_transport).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare the tool destructive and idempotent. The description adds specific detail about replacing an existing skills/ tree, which enriches the behavioral picture without contradicting the annotations.

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

Conciseness5/5

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

The description is well-structured with a concise summary, a detailed behavior paragraph, and a clear return specification. It is neither verbose nor sparse, with all sentences contributing value.

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

Completeness4/5

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

Given the existence of an output schema and the rich annotations, the description is sufficiently complete. It covers purpose, behavior, and return value without elaborating every edge case, which is acceptable.

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

Parameters4/5

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

Schema covers all parameters (100% coverage). The description adds structural context, such as the copy destination pattern and default plugin_name, which goes beyond the schema's individual parameter definitions.

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 clearly states it wraps already-generated skills into an Agent Plugins directory, specifying the action, input, and output. It distinguishes itself from sibling generation tools by noting it does not change generate_* output layout.

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?

It provides clear context on when to use (after skills have been generated) and describes the packaging behavior. It does not explicitly state when not to use it or list alternatives, but the distinction from generate_* tools is implicit.

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