Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get-services

Retrieve services from Illumio PCE using filters like name, port, protocol, or process name to find specific service definitions.

Instructions

Get services from the PCE with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter services by name (supports partial matches)
portNoFilter services by port number
protoNoFilter services by protocol (e.g., tcp, udp)
descriptionNoFilter services by description (supports partial matches)
max_resultsNoMaximum number of services to return
process_nameNoFilter services by process name
egress_process_nameNoReturn only services whose windows_egress_services reference this process (substring, case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.0
    • changedInput schema / properties / description / description
      Previous value: -"Filter services by description"New value: +"Filter services by description (supports partial matches)"
    • addedInput schema / properties / egress_process_name
      Added value: +{
+  "description": "Return only services whose windows_egress_services reference this process (substring, case-insensitive).",
+  "type": "string"
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Maximum number of services to return",
+  "type": "integer"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Filter services by name"New value: +"Filter services by name (supports partial matches)"
  2. Addedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the purpose; it does not explicitly state that this is a read-only operation, has no side effects, how filters combine (AND/OR), what happens with no filters, or any limits. 'Get' implies read-only, but that is not made explicit.

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, tight sentence with no filler. It front-loads the core purpose and filtering capability, making it appropriately concise and easy to parse.

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?

With 7 optional parameters, no output schema, and no annotations, the description is too thin. It does not mention the return shape (e.g., list of services), filter combination logic, pagination, or default behavior for max_results. An agent would have to guess important invocation semantics.

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 7 parameters are already documented in the input schema. The description adds only 'optional filtering' and no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('get') and resource ('services from the PCE'), and mentions optional filtering. It is clear enough to distinguish from sibling mutation tools like create-service, update-service, and delete-service, though it does not explicitly name alternatives or scope nuances.

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?

No explicit when-to-use or when-not-to-use guidance is given. 'Optional filtering' implies this is the tool for retrieving services with filters, but the description does not direct the agent away from or toward any sibling tools, leaving usage context to inference.

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