Skip to main content
Glama
Sign In
phpIPAM MCP Server

phpIPAM MCP Server

by greglg45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_ip_address

Delete an IP address reservation by providing its ID, freeing it for reuse in the IP address management system.

Instructions

Delete/release an IP address reservation.

Args: address_id: ID of the IP address to delete

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": {
      "address_id": "<address_id>"
    },
    "name": "delete_ip_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
address_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

The description only states 'Delete/release' without disclosing any behavioral traits such as irreversibility, required permissions, or potential side effects. Since no annotations are provided, the description fails to convey the destructive nature beyond the verb itself.

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?

The description is extremely concise, consisting of one sentence and a brief Args section. Every word earns its place, with no redundancy or fluff, and the action is front-loaded.

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?

Even with an output schema present, the description lacks essential context for a delete operation. It does not explain reversibility, success/failure conditions, or any impact on associated resources. The minimal information is insufficient for an agent to fully anticipate behavior.

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?

The description repeats the parameter name `address_id` and provides a tautological explanation ('ID of the IP address to delete') that essentially restates the parameter name. It does not specify the ID format, how to obtain it, or any additional context beyond the schema, which has no description for the property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses 'Delete/release' as a specific verb and 'IP address reservation' as the resource, clearly distinguishing it from siblings like `delete_subnet` or `update_ip_address`. It directly states what the tool does without ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or related tools like `reserve_ip_address` or `delete_subnet`, leaving the agent without context for appropriate usage.

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