Retrieve the IPv6 neighbor cache table showing IPv6-to-MAC address mappings via NDP for network monitoring.
Tabel neighbor IPv6 (NDP) — pemetaan IPv6 <-> MAC.
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": "ipv6_neighbors"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral transparency. It only states the output is a table mapping IPv6 to MAC addresses. It does not disclose whether the operation is safe (read-only), whether it refreshes data, or any access requirements. For a simple list tool, this is minimal but acceptable, though more context (e.g., 'shows all neighbors discovered via NDP') would help.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, using a single line. It is front-loaded and communicates the core purpose efficiently. However, it could be slightly more descriptive without losing conciseness, earning a 4 rather than 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and no output schema, the description is the only source of context. It provides the essential mapping (IPv6 to MAC) but lacks details such as whether the list includes all neighbors or is filterable. For a zero-param tool, it is adequately complete but could mention that it returns the full NDP table.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters (schema coverage 100%), so the description does not need to add parameter information. The baseline for 0 parameters is 4, and the description does not fail to add value since there are no parameters to describe.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool displays the IPv6 neighbor table (NDP) mapping IPv6 to MAC addresses. This distinguishes it from sibling tools like 'arp_table' (IPv4 ARP) and 'neighbors' (likely IPv4) by specifying IPv6 and NDP protocol.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. For example, it does not clarify that this lists discovered neighbors via NDP, not configured addresses (which would be 'ipv6_addresses'). The sibling list includes many networking tools, but no usage context is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.