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

ansible-mcp-server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

discover-templates

Identify all infrastructure templates and optionally validate and correct any that are non-compliant.

Instructions

Discover and validate all templates in infrastructure

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": "discover-templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
validateAllNoValidate all discovered templates
fixNonCompliantNoAttempt to fix non-compliant templates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only mentions 'discover and validate'. It does not disclose that 'fixNonCompliant' may modify templates, nor does it explain validation criteria or required permissions.

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 a single concise sentence that front-loads the main action. However, it could be structured to highlight key information like parameters.

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

Completeness2/5

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

Given the two boolean parameters that can trigger validation and fixing, the description is too brief. It does not explain the effects of parameters or the return value, leaving the agent underinformed.

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 coverage is 100% with parameter descriptions, so the baseline is 3. The description adds no additional meaning beyond the schema, repeating the tool's purpose.

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?

The description clearly states the tool discovers and validates templates in infrastructure. However, it does not distinguish from sibling tools like 'discover-ansible-controller' or 'validate-template', which may cause confusion.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternative sibling tools like 'create-compliant-template' or 'fix-template'. The description lacks context for appropriate usage.

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