Skip to main content
Glama

check_role_installed

Verify if an Ansible role is installed in a Ludus cyber range environment, enabling role management for security testing and research.

Instructions

Check if a specific Ansible role is installed.

Uses the ludus CLI with --url when available for reliable remote access. Falls back to HTTP API if CLI is not available. No SSH required.

Args: role_name: Name of the role to check (e.g., "ludus-ad-content", "badsectorlabs.ludus_adcs")

Returns: Dictionary indicating if the role is installed

Example: # Check if a role is installed result = await check_role_installed(role_name="ludus-ad-content")

# If not installed, use install_role() to install it
if not result.get("installed"):
    await install_role(role_name="ludus-ad-content")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_nameYes
Behavior4/5

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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it explains the implementation details (uses ludus CLI with --url, falls back to HTTP API, no SSH required), which helps the agent understand reliability and access methods. It does not mention error handling or performance aspects, but covers key operational traits.

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 well-structured with a clear purpose statement, implementation details, parameter explanation, return value, and an example. It is appropriately sized and front-loaded, though the example section is slightly verbose; every sentence earns its place by adding practical guidance.

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 tool's low complexity (1 parameter, no output schema, no annotations), the description is quite complete: it explains what the tool does, how it works, the parameter, return value, and usage example. It could briefly mention error cases or limitations, but covers the essentials well for a simple check operation.

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

Parameters5/5

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

The schema description coverage is 0%, so the description must compensate fully. It explicitly documents the single parameter 'role_name' with its purpose and provides examples (e.g., 'ludus-ad-content', 'badsectorlabs.ludus_adcs'), adding clear meaning beyond the bare schema. This fully addresses the parameter semantics gap.

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 the specific verb ('check') and resource ('if a specific Ansible role is installed'), making the purpose unambiguous. It distinguishes itself from sibling tools like 'install_role' or 'list_installed_roles' by focusing on checking a single role's installation status rather than installing or listing all roles.

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 provides clear context on when to use this tool: to check if a role is installed, with an example showing it should be followed by 'install_role' if not installed. However, it does not explicitly state when not to use it (e.g., vs. 'list_installed_roles' for bulk checks) or name alternatives, though the example implies a workflow.

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/tjnull/Ludus-FastMCP'

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