Skip to main content
Glama

discover_neighbors

Scan local networks via MNDP to identify MikroTik devices and list neighbor details for connection or inventory tasks.

Instructions

Find MikroTik devices on the local networks via MNDP (like WinBox's Neighbors tab).

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_neighbors"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 mechanism (MNDP discovery) and that it is scoped to the local network, which tells an agent only directly reachable devices will respond. It omits blocking behavior, whether broadcast/multicast must be permitted, and failure modes when nothing answers.

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 verb and resource, and the WinBox analogy earns its place by compressing the whole behavior into a familiar reference. 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?

For a one-parameter read-only discovery tool with an output schema covering the returned devices, the description supplies enough to call it correctly. The main omission is that the `seconds` window is unexplained and results are not contextualized against the sibling router-management tools.

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 `seconds` parameter (default 6), and the description never mentions it. An agent must guess that it is the discovery listen window, and there is no warning that longer values delay the call.

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 ("Find") and resource ("MikroTik devices") with a clear scope ("local networks") and mechanism (MNDP). The WinBox Neighbors analogy makes the function instantly recognizable and implicitly separates it from the ros_*/add_router siblings, though no sibling is named explicitly.

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 context implies this is a discovery step, useful before add_router/list_routers, but the description never says when to use it versus those tools or what to do with the results. Usage is inferred from the "neighbors" framing rather than stated.

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