Skip to main content
Glama

Classify IP address

bursia_ip_classify
Read-onlyIdempotent

Classify an IP address: version and whether it is public, private, loopback, link-local or reserved. Pure computation, free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "<ip>"
    },
    "name": "bursia_ip_classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesAn IPv4 or IPv6 address, e.g. 8.8.8.8 or 2001:db8::1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ip / description
      Added value: +"An IPv4 or IPv6 address, e.g. 8.8.8.8 or 2001:db8::1."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is already met. The description adds genuinely new information — 'pure computation' (no network lookup) and 'free' (no cost/quota) — which is exactly the kind of context annotations cannot express; it only lacks a note on error behavior or return shape.

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?

Two short sentences, zero filler, with the classification categories front-loaded before the operational note. Every clause earns its place.

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, annotated, side-effect-free tool with no output schema, the description covers what it does and what categories it produces. It could be marginally more complete by indicating the return shape (e.g. a version string plus a classification label) or behavior on malformed input, but nothing critical is missing before 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 description coverage is 100% and the schema itself supplies the IPv4/IPv6 examples, so the single 'ip' parameter is fully documented structurally. The description adds no syntax or format guidance beyond the schema, which is the correct baseline 3.

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 (classify) and resource (IP address) and enumerates the exact outputs (version, public/private/loopback/link-local/reserved), so an agent knows precisely what it returns. It does not explicitly differentiate itself from the nearby bursia_cidr_info sibling, which is the only thing keeping it from a 5.

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?

'Pure computation, free' implies it is a cheap local check with no side effects, but the description never says when to choose it over bursia_cidr_info or what to do with invalid input. Usage is inferable from the purpose rather than stated.

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