Retrieve details of a specific enrollment, including its current sequence, step, and next actions. Requires an API key.
Get one enrollment — which sequence, which step, and what happens next. Requires an API key (mk_live_…).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Path parameter `id`. |
Changes observed during successful MCP inspections.
v0.20.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already signals a read-only operation, so the description appropriately adds the API key requirement and the specific fields returned. This is useful additional context beyond annotations, but it doesn't disclose potential errors or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two succinct sentences, with the main verb and resource first, and the auth requirement appended. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter and no output schema, and the description conveys what it returns and the auth requirement. It is complete enough for an agent to call correctly, though it doesn't cover error cases like not found.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter, so the schema already explains id as a path parameter. The description does not add extra meaning about id format or constraints, so it meets the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action and resource: retrieving a single enrollment, and specifies what information is returned (sequence, step, and next actions). This distinguishes it from list_enrollments which returns multiple, and from cancel_enrollment which modifies.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies use when you need details of one specific enrollment identified by id, but does not explicitly name alternatives or exclusion conditions. The context is clear enough given the sibling names, but it could have stated 'use list_enrollments to get all enrollments'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.