mcp-server-systemeio

list_enrollments

Retrieve course enrollments to view which contacts are enrolled in which courses. Supports pagination with cursor and sorting by order.

Instructions

List course enrollments. See which contacts are enrolled in which courses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_enrollments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results (10-100)
`startingAfter`	No	Cursor: ID of last item from previous page
`order`	No	Sort order

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 31, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It implies read-only behavior but does not disclose details like pagination, performance, or potential side effects. The tool likely returns a list, but the description omits behavioral traits.

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 concise with two sentences that front-load the purpose. Every word is earned, and there is no redundancy or unnecessary detail.

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 the tool's simplicity (3 parameters, no output schema), the description is mostly complete. However, it could benefit from mentioning return format or pagination behavior to fully cover agent needs.

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 coverage is 100%, with all parameters adequately described in the schema. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 it lists course enrollments and reveals the association between contacts and courses, distinguishing it from sibling tools like enroll_contact_in_course and remove_enrollment. It is specific and action-oriented.

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 provides clear context for listing enrollments but lacks guidance on when to use this tool versus alternatives or any exclusions. No explicit when-to-use or when-not-to-use information is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server