Skip to main content
Glama

discover_hosts

Ping-sweep an IP, CIDR, or hostname to find live hosts without port scanning, quickly identifying which targets are online before deeper audits.

Instructions

Ping-sweep a target (IP, CIDR, or hostname) to find live hosts without port scanning.

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

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the probing technique (ping sweep, non-port-scanning), which tells the agent this is a shallow, relatively non-intrusive probe. It says nothing about authorization/scope requirements, rate limits, or what happens on large CIDR ranges.

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

Conciseness5/5

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

One sentence with zero filler, front-loading the action and the key scope constraint (no port scanning) before any detail.

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?

An output schema exists, so return values needn't be explained, and the input formats are covered. For a network-probing tool with no annotations, though, the absence of any authorization, rate, or scale guidance leaves a real gap.

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

Parameters4/5

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

The single parameter has 0% schema description coverage (schema only says "Target" string), so the description must compensate, and it does by enumerating the accepted formats: IP, CIDR, or hostname. It does not describe range-size limits or format edge cases.

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

Purpose5/5

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

States a specific verb and resource ("Ping-sweep a target") plus the accepted input forms (IP, CIDR, hostname) and explicitly excludes port scanning, which cleanly separates it from port_scan and service_scan.

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?

The "without port scanning" clause implies this is the lighter-weight host-liveness step, giving some implicit routing away from port_scan. It never states prerequisites such as target being in scope, nor does it name an explicit alternative or exclusion condition.

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