Skip to main content
Glama

security-crypto

ssh_known_hosts_inspect

Inspect ~/.ssh/known_hosts entries for hashed vs plaintext hostnames, deprecated ssh-dss/ssh-rsa keys, and duplicate key fingerprints.

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_known_hosts_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Inspect' plus three specific checks does convey a read-only analytical operation and what findings to expect, but it says nothing about return format, error behavior, or what happens when neither input is provided (presumably defaulting to ~/.ssh/known_hosts, which is only implied by the tool name).

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?

A single front-loaded sentence with no filler; the three checks are listed compactly. The terseness is efficient but contributes to the missing input-mode explanation.

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?

For a low-complexity read-only inspector, the description adequately covers what is analyzed. But with no annotations, no output schema, and zero parameter documentation, the definition leaves the entire input contract unstated, which is the main completeness gap.

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?

Both parameters (text, filePath) have 0% schema description coverage and are never mentioned in the description. The critical distinction – pass raw known_hosts content via text versus a path via filePath – is undocumented anywhere, leaving the agent to guess which parameter to use and whether one overrides the other.

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 specific verb (Inspect) and resource (~/.ssh/known_hosts) and enumerates the exact checks performed: hashed vs plaintext hostnames, deprecated ssh-dss/ssh-rsa keys, and duplicate fingerprints. The resource is distinct enough from siblings like ssh_config_generate_and_audit, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource and the enumerated checks – an agent can infer this is the tool for auditing a known_hosts file. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of how it relates to ssh_config_generate_and_audit, which is the closest sibling in scope.

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