Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get-iplists

Retrieve IP lists from the Illumio PCE using optional filters for name, FQDN, IP address, or description, with a configurable result limit.

Instructions

Get IP lists from the PCE with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqdnNoFilter by FQDN (supports partial matches)
nameNoFilter IP lists by name (supports partial matches)
ip_addressNoFilter by IP address (supports partial matches)
descriptionNoFilter by description (supports partial matches)
max_resultsNoMaximum number of IP lists to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.8.0
    • changedInput schema / properties / description / description
      Previous value: -"Filter by description (optional)"New value: +"Filter by description (supports partial matches)"
    • addedInput schema / properties / fqdn
      Added value: +{
+  "description": "Filter by FQDN (supports partial matches)",
+  "type": "string"
+}
    • addedInput schema / properties / ip_address
      Added value: +{
+  "description": "Filter by IP address (supports partial matches)",
+  "type": "string"
+}
    • removedInput schema / properties / ip_ranges
      Removed value: -{
-  "description": "Filter by IP ranges (optional)",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Maximum number of IP lists to return",
+  "type": "integer"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Filter IP lists by name (optional)"New value: +"Filter IP lists by name (supports partial matches)"
  2. Addedv1.0.0

TDQS

B3.4/5.0
Behavior2/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 only states 'Get', implying a read-only operation, but does not mention authentication requirements, rate limits, default behavior when no filters are applied, pagination, or response format. This is a significant gap for a tool that could have side effects or return large datasets.

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 a single, efficient sentence that front-loads the main action. It contains no extraneous words and gets straight to the point, making it easy for an agent to parse quickly.

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?

For a tool with 5 optional parameters, no annotations, and no output schema, the description is too minimal. It does not explain the default behavior when no filters are provided (e.g., returns all lists), how max_results interacts with pagination, or what the response structure looks like. An agent may not know what to expect from the call.

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?

The schema has 100% description coverage for all parameters, so the baseline is 3. The tool description adds no additional parameter information beyond stating 'optional filtering', which is redundant with the schema. No extra value is provided beyond what the schema already documents.

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 clearly states the verb 'Get', the resource 'IP lists', and the context 'from the PCE'. This distinguishes it from sibling tools like create-iplist, update-iplist, and delete-iplist, making the tool's purpose unambiguous.

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 a read operation but does not explicitly state when to use this tool versus other get tools (e.g., get-rulesets, get-workloads). There is no mention of alternatives or exclusions, leaving usage context largely implied by the name.

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