Skip to main content
Glama

ipv6_status

Read-onlyIdempotent

Retrieve WAN and LAN IPv6 status from a TP-Link modem or router to verify IPv6 connectivity and addressing where the model supports it.

Instructions

WAN and LAN IPv6 status, if the model supports it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description contributes one genuinely behavioral detail - that availability depends on model support - but it does not say how an unsupported model is signaled (error, empty result, or omission), which is the key behavioral question for a conditional tool.

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?

A single short sentence with no filler, and the resource scope is front-loaded ahead of the caveat. The conditional clause is slightly vague in wording but does not waste space.

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?

For a no-argument, read-only status tool with annotations and no output schema, the description is close to sufficient but leaves two things open: what the status payload contains (addresses, prefixes, lease state) and how the 'unsupported model' case manifests to the caller.

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; there is nothing parameter-level for the description to compensate for, and it correctly implies the call is scope-free (both WAN and LAN in one 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?

The description names a specific resource (IPv6 status) and its scope (WAN and LAN), which is more precise than a bare name restatement. It does not explicitly say whether it returns or reports the status, and it does not differentiate itself from the sibling router_status, which likely also surfaces status information.

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 clause 'if the model supports it' hints at a precondition for calling, which is useful. However, there is no explicit when-to-use guidance and no routing to or away from alternatives such as router_status, leaving usage to inference.

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