Skip to main content
Glama

configure_ssh_role_installation

Set up SSH access to automate role installation on Ludus servers, enabling direct cloning and deployment without manual configuration.

Instructions

Configure SSH access for automatic role installation on Ludus server.

This allows the MCP server to automatically clone and install directory-based roles (like ludus-ad-content) directly on the Ludus server via SSH, without manual setup.

Security Note: SSH access requires appropriate permissions. Use SSH keys when possible.

Args: ssh_host: SSH hostname or IP address of the Ludus server ssh_user: SSH username (default: "root") ssh_key_path: Path to SSH private key file (preferred over password) ssh_password: SSH password (less secure, only use if key is not available) allow_ssh_install: Enable automatic SSH-based installation (default: True)

Returns: Configuration result with status

Example: # Configure with SSH key (recommended) result = await configure_ssh_role_installation( ssh_host="192.168.10.3", ssh_user="root", ssh_key_path="~/.ssh/id_rsa", allow_ssh_install=True )

# Configure with password (less secure)
result = await configure_ssh_role_installation(
    ssh_host="192.168.10.3",
    ssh_user="root",
    ssh_password="your-password",
    allow_ssh_install=True
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ssh_hostYes
ssh_userNoroot
ssh_key_pathNo
ssh_passwordNo
allow_ssh_installNo
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. It discloses key behavioral traits: the tool configures access for automatic installation, requires appropriate permissions, recommends SSH keys for security, and allows enabling/disabling installation. It mentions that SSH password is less secure but does not cover rate limits, error handling, or detailed response format.

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, security note, parameter explanations, return info, and examples. It is appropriately sized but could be slightly more concise by integrating some details; every sentence adds value, though the example section is lengthy but useful.

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 complexity (configuration tool with security implications), no annotations, no output schema, and 0% schema coverage, the description is largely complete. It covers purpose, usage, parameters, and security, but lacks details on return values (only mentions 'Configuration result with status') and potential errors or side effects.

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?

Schema description coverage is 0%, so the description must compensate. It adds significant meaning beyond the schema by explaining each parameter's purpose (e.g., 'SSH hostname or IP address', 'SSH username', 'Path to SSH private key file'), security implications, defaults, and usage in examples, fully documenting all 5 parameters.

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 tool's purpose with specific verbs ('configure SSH access') and resources ('automatic role installation on Ludus server'). It distinguishes from siblings by focusing on SSH configuration for role installation, unlike tools like 'install_role' or 'configure' general tools in the list.

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 (for automatic SSH-based role installation on Ludus server) and includes a security note recommending SSH keys. However, it does not explicitly state when not to use it or name specific alternatives among the many sibling tools.

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