Skip to main content
Glama

network_inventory

Identifies live hosts on a target and runs a quick service scan only on hosts that respond.

Instructions

Sweep a target for live hosts, then run a quick service scan on just the hosts that respond.

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

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the meaningful two-phase sequencing — scanning only hosts that respond, which bounds the scan surface and noise. It says nothing about authorization/scope requirements, scan intensity, or whether the sweep is active/aggressive, which matter for network tooling.

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, front-loaded with the primary action and ordered as the operation actually executes. No filler or restated name.

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 composite nature is covered. However, for a network-scanning tool with zero annotations and an undocumented target parameter, the definition omits target format and scope/authorization context needed to invoke it safely and correctly.

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% for the single required 'target' parameter, so the schema adds nothing. The description does not clarify the accepted format (single IP, CIDR block, hostname, or range), which is the key ambiguity for a network sweep tool.

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 names a specific compound operation: sweep a target for live hosts, then run a quick service scan on the responders. An agent can tell this is discovery plus light enumeration, but nothing distinguishes it from siblings like discover_hosts or quick_scan, leaving the boundary implicit.

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 statement of when to use this composite tool versus running discover_hosts and service_scan/quick_scan separately, and no prerequisites or exclusions. The only contextual hint is the phrase 'quick service scan', which implies light rather than deep enumeration.

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