Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get-rulesets

Retrieve security rulesets from the Illumio PCE with optional filters for name, labels, enabled status, description, and result limits.

Instructions

Get rulesets from the PCE with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter rulesets by name (supports partial matches)
labelsNoJSON-encoded list of label URIs to filter by scope
enabledNoFilter by enabled/disabled status
descriptionNoFilter rulesets by description (supports partial matches)
max_resultsNoMaximum number of rulesets to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.0
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Filter rulesets by description (supports partial matches)",
+  "type": "string"
+}
    • changedInput schema / properties / enabled / description
      Previous value: -"Filter by enabled/disabled status (optional)"New value: +"Filter by enabled/disabled status"
    • addedInput schema / properties / labels
      Added value: +{
+  "description": "JSON-encoded list of label URIs to filter by scope",
+  "type": "string"
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Maximum number of rulesets to return",
+  "type": "integer"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Filter rulesets by name (optional)"New value: +"Filter rulesets by name (supports partial matches)"
  2. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description itself indicates a read operation ('Get'), but it does not disclose filters' combine behavior (AND vs OR), pagination, or that it returns a list. It is adequate but minimal.

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 one short sentence that includes the core purpose and key feature (filtering) with no fluff. It is appropriately front-loaded.

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?

Given no output schema, the tool is a simple list operation with all parameters documented. The description is slightly sparse but sufficient for an agent to call it correctly; the lack of pagination details is minor.

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%, so all five parameters are described in the schema. The description adds no extra param semantics beyond what the schema provides, matching the baseline of 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?

The description clearly states the action (Get) and the resource (rulesets from the PCE), and mentions filtering. It is specific enough to distinguish from sibling tools like create-ruleset or delete-ruleset, though it does not explicitly name any sibling.

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 this is a read-only query tool with optional filtering, but it does not state when to use it versus alternatives (e.g., get-rulesets for listing vs. update-ruleset for modifying). No explicit conditions or exclusions are provided.

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