Skip to main content
Glama

ssh_audit

Check SSH algorithm support and host key fingerprints on a target to identify weak configurations and verify host identity.

Instructions

Check SSH algorithm support and host key fingerprints on a target.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "ssh_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNo22
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. The word 'Check' implies a passive read, but the description never states that it is non-destructive, whether it needs credentials, how long it takes, or what happens on an unreachable host. Beyond the two things it inspects, the agent knows nothing about side effects or failure modes.

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 tight sentence with the core scope front-loaded and no filler. It is efficient, but the brevity is achieved partly by dropping information the parameters and annotations do not supply elsewhere.

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 two-parameter network probe with no annotations and zero schema coverage, the definition is thin. Because an output schema exists, return values need not be explained, but the target format, the meaning of the ports parameter, and the safety/credential profile are all missing.

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?

Schema description coverage is 0%, so the description must compensate and it largely does not. It mentions 'target' only implicitly through 'on a target' with no format (hostname/IP/CIDR), and the 'ports' parameter — including the default of 22 and whether it accepts ranges or comma lists — is never mentioned at all.

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?

The description states a specific verb and resource: 'Check SSH algorithm support and host key fingerprints on a target.' That is concrete enough to separate it from ssl_audit or rdp_audit by protocol, though it never names a sibling or states explicitly that it is SSH-only rather than a generic crypto check.

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 at all: no prerequisites, no exclusions, no pointer to alternatives such as ssl_audit or port_scan for related checks. The agent must infer from the tool name alone that this is the SSH-specific audit path rather than the SSL one.

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