Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get-labels

Retrieve labels from Illumio PCE with optional filters for key, value, usage, deleted status, and result limit. Use to list and manage label definitions for security policy and workload operations.

Instructions

Get labels from the PCE with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoFilter by label key/type, matched exactly (e.g., 'role', 'app', 'env', 'loc'). 'role' will not match 'servicerole'
usageNoInclude label usage flags
valueNoFilter by label value (supports partial matches)
max_resultsNoMaximum number of labels to return
include_deletedNoInclude deleted labels

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.8.0
    • addedInput schema / properties / include_deleted
      Added value: +{
+  "description": "Include deleted labels",
+  "type": "boolean"
+}
    • addedInput schema / properties / key
      Added value: +{
+  "description": "Filter by label key/type, matched exactly (e.g., 'role', 'app', 'env', 'loc'). 'role' will not match 'servicerole'",
+  "type": "string"
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Maximum number of labels to return",
+  "type": "integer"
+}
    • removedInput schema / properties / name
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / usage
      Added value: +{
+  "description": "Include label usage flags",
+  "type": "boolean"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Filter by label value (supports partial matches)",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[]
  2. Addedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It communicates a read-only list operation with optional filtering, but it does not disclose response format, pagination behavior, or default handling of deleted labels. This is minimal but not misleading.

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, front-loaded sentence with no filler. It conveys the resource, operation, and key capability without redundant elaboration.

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

Completeness3/5

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

For a simple list tool with well-documented optional parameters, the description is adequate but lean. It does not mention what a label is, what the response looks like, or any default behavior, which matters since there is no output schema and no annotations.

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 the schema already documents all five parameters clearly. The description adds no parameter-specific meaning beyond calling the filters 'optional,' which is appropriate but does not elevate the score.

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 a specific verb ('Get') and resource ('labels') with a clear source ('PCE'), and optional filtering is mentioned. It is immediately distinguishable from the label mutation tools like create-label, update-label, and delete-label.

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 the tool to use when retrieving labels, but it does not explicitly state when to use it over alternatives or when not to use it. It provides no exclusions or comparative guidance, so usage context is only implied.

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