Skip to main content
Glama
Sign In
phpIPAM MCP Server

phpIPAM MCP Server

by greglg45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_subnet_details

Retrieve detailed subnet information by ID, with optional IP address listing up to a specified limit.

Instructions

Get detailed information about a specific subnet.

CONTEXT OPTIMIZATION: Address listing limited to 10 by default.

Args: subnet_id: Subnet ID to get details for include_addresses: Include IP addresses in the subnet (default: False) address_limit: Max addresses to show if include_addresses=True (default: 10)

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": {
      "subnet_id": "<subnet_id>"
    },
    "name": "get_subnet_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
subnet_idYes
address_limitNo
include_addressesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds one valuable behavior: address listing is limited to 10 by default ('CONTEXT OPTIMIZATION'). However, it does not explicitly state that the operation is read-only or describe error/edge-case behavior, leaving some transparency gap.

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?

The description is compact and front-loaded with a clear summary, followed by a prominent context note and an Args block. The Args section somewhat duplicates schema metadata, but it is justified here because the schema lacks parameter descriptions.

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 simple read-style tool with an output schema present, the description covers the tool's purpose, key default behavior (address limit), and all parameters. It lacks explicit alternative-tool guidance, but the sibling list provides enough context for a capable agent to select it.

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?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter in plain language. It clarifies the conditional relationship between include_addresses and address_limit (address_limit only applies when include_addresses=True), which the schema's titles and defaults do not convey.

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 opening sentence uses a specific verb and resource ('Get detailed information about a specific subnet'), clearly indicating this tool targets one subnet by ID. It is distinct from sibling list/search/subnet tools by scope, but does not explicitly contrast itself with them.

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 description implies usage context: call this when you have a subnet_id and want details for that specific subnet. It gives no explicit guidance about when to prefer this over get_section_subnets or search_subnets, and no exclusion criteria.

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

Deploy Server

Other Tools