Skip to main content
Glama

List My Enrollments

list_my_enrollments
Read-onlyIdempotent

List your enrollments across all courses to view role, section, state, and current grade summary. Read-only; use it when you need per-enrollment roles or sections rather than course details.

Instructions

List your enrollments across all courses, with role (student, observer…), section and current grade summary. Read-only. Use list_courses for course details; use this when you need roles, sections or per-enrollment grades.

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_my_enrollments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
typeNoOptional enrollment type filter, e.g. "StudentEnrollment".
limitNoMaximum number of items to return (one page of results). Smaller is faster.
stateNoactive, invited, completed, inactive

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • addedInput schema / properties / type / description
      Added value: +"Optional enrollment type filter, e.g. \"StudentEnrollment\"."
  3. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

The 'Read-only' note restates readOnlyHint=true and adds nothing the annotations don't already say. It does disclose what each enrollment row contains (role, section, grade summary), which is genuinely useful given there is no output schema, but it says nothing about result volume, ordering, or how the page/limit pair behaves in practice beyond what the schema already documents.

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?

Two compact sentences with zero filler: the capability and its returned fields come first, the sibling routing second. No sentence is expendable.

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?

For a read-only, zero-required-parameter list tool, the description covers purpose, returned fields, and sibling disambiguation, and the schema handles pagination. The only remaining gap — ordering and typical result size — is minor and partly mitigated by the page/limit descriptions.

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 page/limit/type/state are already fully documented. The description alludes to roles and sections but does not map them to the 'type' or 'state' filters or give example values beyond what the schema's own enum listing provides. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource ('List your enrollments across all courses') and immediately enumerates the distinguishing payload — role, section, grade summary — that separates it from list_courses. An agent can pick this tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative ('use list_courses for course details') and states the selection condition ('use this when you need roles, sections or per-enrollment grades'). This is the when/when-not/alternative pattern done properly.

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