Skip to main content
Glama

install_role_from_url

Install Ansible roles from custom Git repositories not available on Ansible Galaxy. Clone and set up roles directly from Git URLs with optional branch specification.

Instructions

Install an Ansible role from a custom Git repository URL.

Use this to install roles from custom Git repositories that are not on Ansible Galaxy. The repository will be cloned on the Ludus server and installed.

Args: role_name: Name to give the role when installed git_url: Git repository URL (e.g., "https://github.com/user/my-role") branch: Optional branch/tag to checkout (default: main/master)

Returns: Installation result with status and instructions

Examples: # Install a custom role from GitHub result = await install_role_from_url( role_name="my-custom-role", git_url="https://github.com/myorg/ludus-custom-role" )

# Install from a specific branch
result = await install_role_from_url(
    role_name="my-role-dev",
    git_url="https://github.com/myorg/ludus-custom-role",
    branch="develop"
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_nameYes
git_urlYes
branchNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the repository will be cloned on the Ludus server and installed, which adds useful context about the installation process. However, it lacks details on permissions, error handling, or rate limits, which are important for a tool that performs installations.

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, usage guidelines, parameter explanations, and examples. It is appropriately sized, though the examples section is detailed, which is helpful but slightly reduces conciseness.

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

Completeness3/5

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

Given the complexity of installing roles from Git, no annotations, and no output schema, the description is moderately complete. It covers purpose, usage, and parameters well but lacks details on return values (only mentions 'Installation result with status and instructions' vaguely) and potential side effects or errors.

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?

With 0% schema description coverage, the description compensates by explaining all three parameters: 'role_name' (name to give the role when installed), 'git_url' (Git repository URL with an example), and 'branch' (optional branch/tag to checkout with default). This adds significant meaning beyond the bare schema.

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 action ('Install an Ansible role') and resource ('from a custom Git repository URL'), distinguishing it from sibling tools like 'install_galaxy_role' or 'install_role' by specifying the source as custom Git repositories not on Ansible Galaxy.

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 explicitly states when to use this tool ('Use this to install roles from custom Git repositories that are not on Ansible Galaxy'), providing clear context. However, it does not mention when not to use it or explicitly name alternatives like 'install_galaxy_role' for Galaxy-based roles.

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