Skip to main content
Glama
Sign In
ansible-mcp-server

ansible-mcp-server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

discover-network-devices

Identify and classify devices on a network subnet, with the ability to skip known devices.

Instructions

Discover devices on the network and classify them

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": "discover-network-devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
subnetNoNetwork subnet to scanYOUR_NETWORK_SUBNET
knownDevicesNoKnown devices to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, runtime, side effects, or data returned. 'Discover' implies scanning but no safety or scope details.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure and does not front-load critical details. It could be improved without adding length.

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?

Without output schema or annotations, the description fails to explain what 'classify' means, the output format, or any constraints (e.g., subnet syntax). This leaves the agent underinformed for correct invocation.

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 descriptions already cover both parameters (subnet and knownDevices) with clear intent. The description adds no extra meaning beyond what the schema provides, meeting the baseline for 100% coverage.

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?

Description clearly states the verb (discover, classify) and resource (network devices). It is specific enough to differentiate from general hardware scanning tools, though not from 'network-interfaces' or other network-specific tools.

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?

No guidance on when to use this tool versus alternatives. The description lacks explicit context about prerequisites, scope, or comparison to siblings like 'hardware-inventory' or 'network-interfaces'.

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