Skip to main content
Glama

net-web-media

ipv6_cidr_calculate

Expand compressed IPv6 addresses to full 128-bit hextets, classify scope (link-local, ULA, global, multicast), and compute network prefix range.

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

Input Schema

NameRequiredDescriptionDefault
textNo
addressNo2001:db8::1/64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description bears the full disclosure burden. It does convey that this is a stateless computation by enumerating exactly what gets derived (full hextets, scope classification, prefix range), which implies no mutation. However, it says nothing about the output shape, how invalid or bare addresses are handled, or whether passing no address falls back to the default - all material for a parsing tool with zero annotation coverage.

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?

One sentence, front-loaded with the primary action and no filler. It is dense but every clause carries an actual operation, and the list structure makes the three capabilities easy to scan.

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?

With no annotations, no output schema, and 0% parameter documentation, the description must compensate for all three and does not. The ambiguous 'text' versus 'address' parameters and the undisclosed return format leave an agent guessing at invocation details, which is a significant gap for even a simple two-parameter tool.

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% and the description never mentions either parameter. The two parameters are named 'text' and 'address' and are both strings with no documented relationship, so an agent cannot tell whether they are synonyms, precedence-ordered, or serve different purposes - the single most important ambiguity in this definition is left unaddressed.

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 three specific operations on a specific resource: expand to 128-bit hextets, classify scope, and compute network prefix range. That is far more informative than a tautology, and the IPv6 prefix in the tool name separates it from the ipv4_* siblings without the description needing to. It stops short of 5 only because it doesn't state whether all three operations run together or whether the caller selects one.

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?

There is no when-to-use guidance at all: nothing about when an agent should pick this over ipv4_cidr_range_expand or ipv4_subnet_calculate, no prerequisites, and no statement of what input formats are accepted. The only usable signal is the IPv6-versus-IPv4 distinction implied by the tool name rather than the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources