Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete-iplist

Delete an IP List from the Illumio PCE using its href or name. Removes the specified list from security policy to clean up unused resources.

Instructions

Delete an IP List from the PCE. Provide either 'href' or 'name' (but not both) to identify the IP List. WRITE OPERATION: changes PCE state. In clients that gate tool calls (Claude Desktop, Claude Code), this pauses for the user to approve it -- the call has not failed and must not be retried while waiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hrefNoHref of the IP List to delete (e.g., /orgs/1/sec_policy/draft/ip_lists/123)
nameNoName of the IP List to delete (alternative to href)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • removedInput schema / oneOf
      Removed value: -[
-  {
-    "required": [
-      "href"
-    ]
-  },
-  {
-    "required": [
-      "name"
-    ]
-  }
-]
    • changedInput schema / properties / href / description
      Previous value: -"Href of the IP List to delete"New value: +"Href of the IP List to delete (e.g., /orgs/1/sec_policy/draft/ip_lists/123)"
  2. Addedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly labels the operation as a WRITE OPERATION that changes PCE state, and discloses that gated clients pause for user approval, warning that the call has not failed and must not be retried. This is exactly the behavioral context an agent needs beyond the action 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?

Three tight sentences, each earning its place: action, parameter selection rule, and critical behavioral warning. The most important information is front-loaded, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with two optional parameters and no output schema, the description fully equips an agent to invoke it correctly. It covers resource, identification method, exclusivity constraint, operation type, and client-side behavior. Nothing essential is missing.

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 coverage is 100% and both parameters have descriptions, so the baseline is 3. The description adds meaningful value by specifying the exclusive-or relationship between 'href' and 'name' ('but not both'), which is not captured in the schema itself.

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 opens with a specific verb and resource: 'Delete an IP List from the PCE.' This clearly distinguishes it from sibling tools like create-iplist, update-iplist, and get-iplists. No ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs how to identify the resource: provide either 'href' or 'name' but not both. It clearly states the context for use ('Delete an IP List from the PCE'). It does not explicitly name exclusions or alternatives, but the operation is unambiguous and the identification rule is strong guidance.

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