kvm-pilot

ssh_discover

Read-onlyIdempotent

Scan an authorized CIDR range to find hosts with an open SSH port when a target address is unknown. Requires confirm=true before the scan runs.

Instructions

Scan a CIDR for hosts with an open SSH port. RISKY — opt-in.

An active network scan: noisy, and only acceptable on networks the user owns or is authorized to probe. Use it ONLY to help find a target whose address the user doesn't know, after they confirm the range — never by default. confirm=true is required to acknowledge the scan.

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": {
      "cidr": "<cidr>"
    },
    "name": "ssh_discover"
  }
}

Input Schema

Name	Required	Description
`cidr`	Yes	Network to scan in CIDR form, e.g. '10.0.1.0/24'. The user must own or be authorized to probe it.
`port`	No	TCP port to probe.
`confirm`	No	Per-invocation approval when the client cannot prompt a human: set true to approve this exact call under the operator's standing policy. Leave false when the client supports elicitation (a human is asked). Never pre-set it speculatively; a denial returns outcome=not_confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Oct 19, 2026

addedInput schema / properties / cidr / description

Added value: +"Network to scan in CIDR form, e.g. '10.0.1.0/24'. The user must own or be authorized to probe it."

addedInput schema / properties / confirm / description

Added value: +"Per-invocation approval when the client cannot prompt a human: set true to approve this exact call under the operator's standing policy. Leave false when the client supports elicitation (a human is asked). Never pre-set it speculatively; a denial returns outcome=not_confirmed."

addedInput schema / properties / port / description
```
Added value: +"TCP port to probe."
```
addedInput schema / properties / port / maximum
```
Added value: +65535
```
addedInput schema / properties / port / minimum
```
Added value: +1
```

First observedv0.1.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, idempotent), and the description adds what they cannot: the scan is noisy, requires the user to own the range, demands confirm=true, and returns outcome=not_confirmed on denial. That is genuine operational context beyond structured fields.

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 purpose and the RISKY flag are front-loaded in the first line, then authorization and the confirm requirement follow in descending priority. Slightly redundant with the schema's confirm description, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter discovery tool with no output schema, the description covers purpose, risk, authorization, and the failure mode of a missing confirmation. It does not indicate the shape of a successful result (host list, timing), a minor gap given there is no output schema to lean on.

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 coverage is 100% and every parameter already carries a detailed description, including the nuanced confirm/elicitation behavior. The description restates that confirm=true is required but adds no syntax or format detail the schema lacks, so baseline 3 applies.

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?

Opens with a specific verb+resource+scope: 'Scan a CIDR for hosts with an open SSH port.' That cleanly separates CIDR-wide discovery from the single-target check implied by the ssh_reachable sibling. It stops short of naming that sibling explicitly, so an agent must infer the routing rather than read it.

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

Usage Guidelines5/5

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

Gives an explicit positive condition (only to find a target whose address the user doesn't know, after they confirm the range) and an explicit exclusion (never by default), plus the authorization precondition. This is exactly the when/when-not guidance an agent needs for a risky tool.

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