Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

network_scan

Read-only

Discovers devices on the local subnet by probing every address to return IP, MAC, and hostname details. Use it to answer questions about which machines are currently online.

Instructions

Scan the local network to discover devices (IP, MAC, hostname). It probes every address on the subnet and takes up to 30 seconds, so it is an answer to a question somebody asked rather than a way to begin. Inside a container it refuses, because the subnet it would scan is the container's own

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuine context on top: it probes every address on the subnet, can take up to 30 seconds, and hard-refuses inside a container. That duration and refusal behavior is exactly the kind of thing an agent needs before calling and is not available in the 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?

Three compact clauses with the capability front-loaded, then the cost, then the failure mode. The middle clause ('an answer to a question somebody asked rather than a way to begin') is slightly colloquial but carries real routing value, so nothing 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?

With no output schema, the description correctly names what discovery yields (IP, MAC, hostname), plus timing and the container refusal. It stops short of stating privilege requirements or result-size expectations, which for a full-subnet sweep would be useful, but nothing essential is missing.

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 tool takes zero parameters, so the baseline is 4. The description adds no parameter detail because there is none to add, and it does not need to.

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 and resource ('Scan the local network to discover devices') and even enumerates the returned fields (IP, MAC, hostname). It is clear about what it does, but it never distinguishes itself from adjacent siblings like inventory_scan or open_ports, leaving the agent to infer the boundary.

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

Usage Guidelines4/5

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

Gives real when-to-use framing ('an answer to a question somebody asked rather than a way to begin') and an explicit when-not condition (refuses inside a container because the subnet would be the container's own). No alternative tool is named for either the host-discovery or the port-scanning case, so routing still requires inference.

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

Deploy Server

Other Tools