Skip to main content
Glama

security-crypto

ssh_config_generate_and_audit

Generate hardened ~/.ssh/config stanzas (JumpHost/ProxyJump, IdentityFile, IdentitiesOnly, ServerAliveInterval) or audit existing SSH configs.

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

Input Schema

NameRequiredDescriptionDefault
portNo
textNo
userNoubuntu
aliasNoprod
hostNameNo10.0.0.10
proxyJumpNo
identityFileNo~/.ssh/id_ed25519

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. 'Generate hardened stanzas' does not say whether the tool writes to ~/.ssh/config on disk or just returns text, whether existing files are overwritten, or what 'hardened' concretely means beyond the directive names.

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?

One tight sentence, front-loaded with the primary action and the directives involved. Not padded, though the brevity comes at the cost of the missing detail rather than being a virtue in itself.

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?

For a 7-parameter, dual-mode tool with no annotations, no output schema, and zero schema description coverage, the single sentence leaves too much unspecified: mode selection, file side effects, defaults behavior, and the purpose of 'text' and 'alias' all remain unknown.

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

Parameters2/5

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

Seven parameters at 0% schema coverage. The description names config directives (ProxyJump, IdentityFile, IdentitiesOnly, ServerAliveInterval) rather than parameters, leaving alias, hostName, user, port, and especially 'text' — the likely audit input — entirely undefined. Meaning added beyond the schema is minimal.

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

Purpose4/5

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

States a concrete verb and resource: generating hardened ~/.ssh/config stanzas with named directives, plus an audit mode. The audit half is only a clause with no object details, but the primary purpose is unmistakable and distinguishable from crypto/x509 siblings.

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 guidance on when to generate versus when to audit, and no hint which parameter selects the mode (presumably 'text', never stated). No prerequisites, no mention of whether an existing config must be supplied or is read from disk.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources