Skip to main content
Glama
Systems Manager

Systems Manager

Add Authorized Key

sm_advanced_add_authorized_key
Destructive

Adds an authorized SSH public key to a system, enabling key-based access for remote host administration and orchestration.

Instructions

Add authorized key (sm_advanced_operations). Operations for SSH and specialized managers

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

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
public_keyNoPublic key content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it doesn't say the key is appended to an SSH authorized_keys file, that re-running creates duplicates (non-idempotent), or when the confirm flag is required. It is not contradictory, merely silent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, which is good. But the second sentence is filler that restates the tool's category rather than earning its place, and the parenthetical duplicates the title.

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 destructive, non-idempotent mutation with no output schema, so the description should explain what changes on the system and what the caller gets back. Neither is covered, leaving the agent to guess at side effects and result format.

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% with only two parameters, so the schema already explains public_key and confirm adequately. The description adds no extra meaning about accepted key formats or confirmation semantics, which is the baseline expectation when the schema carries the burden.

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 phrase 'Add authorized key' gives a verb and a resource, so the basic action is inferable. However, it never states scope: which user's authorized_keys file, which host, or whether it appends versus overwrites. The trailing '(sm_advanced_operations). Operations for SSH and specialized managers' is namespace boilerplate that adds no distinguishing information versus siblings like sm_advanced_create_venv.

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 when-to-use guidance, no prerequisites (e.g. SSH must be configured, key must be pre-generated), and no mention of alternatives. The description gives the agent no basis for choosing this tool over any other advanced-management sibling.

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