Skip to main content
Glama
Sign In
ansible-know-mcp

ansible-know-mcp

by leogallego
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Generate Plugin Skill

generate_plugin_skill
Idempotent

Generates a SKILL.md skill package for one Ansible plugin using its name and type, writes it to disk, and returns the content or an error.

Instructions

Generate a skill package for one plugin.

Writes SKILL.md to disk (no scripts/ or assets/). Returns the SKILL.md content as str, or {"error": str} on failure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plugin_name": "<plugin_name>",
      "plugin_type": "<plugin_type>"
    },
    "name": "generate_plugin_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
install_toNoOptional absolute path to install the skill to. Defaults to the project skills/ directory (via ANSIBLE_KNOW_SKILLS_DIR, or ANSIBLE_KNOW_PROJECT_DIR/CLAUDE_PROJECT_DIR/cwd + /skills).
plugin_nameYesFully-qualified plugin name (e.g. 'netbox.netbox.nb_lookup')
plugin_typeYesPlugin type (lookup, filter, test, connection, become, strategy, callback, inventory, cache, cliconf, httpapi, netconf, shell, or vars)
collection_handleNoSession handle returned by ensure_collection. Omit on local stdio; required on remote.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / collection_handle
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Session handle returned by ensure_collection. Omit on local stdio; required on remote."
+}
  2. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / install_to / description
      Previous value: -"Optional absolute path to install the skill to"New value: +"Optional absolute path to install the skill to. Defaults to the project skills/ directory (via ANSIBLE_KNOW_SKILLS_DIR, or ANSIBLE_KNOW_PROJECT_DIR/CLAUDE_PROJECT_DIR/cwd + /skills)."
  3. First observedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds meaningful behavior beyond the lone idempotentHint annotation: it discloses the disk side effect (writes SKILL.md), the boundaries of what is written (no scripts/ or assets/), and the failure mode ({'error': str}). It does not mention permission or overwrite behavior for an idempotent write, but the core operational traits are covered.

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?

Three short lines, front-loaded with the purpose and followed by side effects and return shape. No filler or redundancy.

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?

An output schema exists so return-value explanation isn't required, and the description still covers the write side effect and error shape. The main gap is missing guidance on prerequisites such as the collection_handle requirement on remote sessions, which is only in the schema.

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% and each parameter is documented in-schema, so the baseline of 3 applies. The description adds no parameter-level meaning (e.g., how plugin_name/plugin_type interact or when install_to is needed) beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('Generate a skill package for one plugin') and scopes it to a single plugin, which implicitly separates it from the role/collection skill generators. It does not name those siblings explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance; the agent must infer from the name and the 'one plugin' scope that generate_skill, generate_role_skill, and generate_collection_skills are the alternatives. Usage is implied by scope only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools