Skip to main content
Glama

Configure Key Auth

tm_inventory_configure_key_auth

Configure SSH key authentication across hosts defined in a YAML inventory group, distributing a shared public key to enable passwordless login.

Instructions

Configure key auth (tm_inventory). Bulk inventory operations against YAML host groups.

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": "tm_inventory_configure_key_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
cfgNoLocal SSH config path (copy_ssh_config).
cmdNoShell command (run_command).
keyNoShared key path (configure_key_auth)./app/.ssh/id_ed25519
hostNorun_command only. Optional single-host alias to target instead of the whole 'group' fan-out — the safe way to reach ONE inventory host (e.g. 'gb10') without running against 'homelab'. Resolved and authorized through the same alias store tm_remote/tm_hosts use, so the two are one source of truth: an unknown or unauthorized alias is rejected outright, never silently skipped. Takes precedence over 'group' when set.
groupNoTarget group.all
lpathNoLocal file path (send_file).
rpathNoRemote file path (send_file/receive_file).
key_pfxNoPrefix for new keys (rotate_key)./root/.ssh/id_
previewNorun_command only. If true, resolve the exact target host(s) for 'host'/'group' and return them in 'resolved_hosts' WITHOUT running 'cmd' — lets a caller verify scope before executing for real (no surprise fan-out). The real (non-preview) response also always includes 'resolved_hosts' for the same reason.
rmt_cfgNoRemote config path (copy_ssh_config)./root/.ssh/config
timeoutNoCommand timeout in seconds.
key_typeNoKey type: rsa or ed25519.ed25519
parallelNoRun parallel.
inventoryNoYAML inventory path (default: $XDG_CONFIG_HOME/scion-sdk/inventory.yml)./root/.config/scion-sdk/inventory.yml
max_threadsNoMax threads.
lpath_prefixNoLocal dir prefix (receive_file).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.7
    • changedInput schema / properties / inventory / default
      Previous value: -"/root/.config/agent-connectors/inventory.yml"New value: +"/root/.config/scion-sdk/inventory.yml"
    • changedInput schema / properties / inventory / description
      Previous value: -"YAML inventory path (default: $XDG_CONFIG_HOME/agent-connectors/inventory.yaml)."New value: +"YAML inventory path (default: $XDG_CONFIG_HOME/scion-sdk/inventory.yml)."
  2. Addedv3.3.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. However, the description adds almost no behavioral context: it does not say what remote state is modified, whether authorized_keys is updated, what permissions are required, or how failures are handled.

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 short and front-loads the action name. The second sentence is somewhat vague and potentially misleading, but the overall structure is efficient and not bloated.

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?

This is a complex mutation tool with 16 parameters, many siblings, and an output schema. The description is too sparse to explain the tool's operational scope, prerequisites, or relationship to the inventory and remote-key siblings, leaving the agent to infer too much from the schema and annotations.

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 description coverage is 100%, so the input schema already documents all 16 parameters in detail. The description adds no parameter-specific meaning beyond the schema, which is acceptable at the baseline for fully documented schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action, 'Configure key auth', but the second sentence, 'Bulk inventory operations against YAML host groups', is broad enough to describe many sibling tools. It does not clarify what configuring key auth actually entails or distinguish this tool from related siblings such as tm_remote_setup_passwordless or tm_remote_test_key_auth.

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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Bulk inventory operations against YAML host groups' implies a bulk inventory context, but it does not state prerequisites, exclusions, or which sibling to choose for single-host or test-only key-auth operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.