Skip to main content
Glama
Sign In
MCP SysOperator

MCP SysOperator

by MCP-Mirror
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_ad_hoc

Execute Ansible ad-hoc commands to manage infrastructure on specified hosts, enabling quick configuration changes and system administration tasks.

Instructions

Run an Ansible ad-hoc command against specified hosts

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": {
      "pattern": "<pattern>"
    },
    "name": "run_ad_hoc"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes
moduleNoshell
argsNo
inventoryNo
becomeNo
extra_varsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions running commands against hosts, implying execution and potential system changes, but fails to detail critical aspects like permissions needed, side effects, error handling, or output format, leaving significant gaps for a tool with 6 parameters.

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 a single, efficient sentence with no wasted words, making it highly concise and front-loaded. Every part contributes directly to stating the tool's function, though this brevity comes at the cost of detail.

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 tool's complexity (6 parameters, no output schema, no annotations), the description is incomplete. It doesn't cover parameter meanings, behavioral traits, or usage context, making it inadequate for an agent to reliably invoke this tool without additional guesswork or external knowledge.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only vaguely references 'specified hosts' (hinting at 'pattern' or 'inventory'), but doesn't explain any of the 6 parameters (e.g., 'args', 'become', 'extra_vars'), their purposes, or how they interact, failing to add meaningful semantic value beyond the bare 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?

The description clearly states the verb ('Run') and resource ('Ansible ad-hoc command against specified hosts'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'run_playbook' or 'list_tasks', which are related Ansible operations, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'run_playbook' for playbooks or 'list_tasks' for task listing. It lacks context on prerequisites, exclusions, or specific scenarios, offering only a basic statement of function.

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