Retrieve your registered TUMonline courses with course number, title, type, semester, and lecturers. Use it to review your current course list; read-only and requires the lectures right.
List courses from wbservicesbasic.veranstaltungenEigene: LV number, title, type, semester, and lecturers. Requires the lectures right. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
It informs the agent of a critical prerequisite ('Requires the lectures right') that is behavioral context regarding authorization, which is not captured by the existing boolean annotations. This is vital for ensuring the tool call will succeed.
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?
The description is highly efficient, utilizing a single sentence to cover the data source, the specific fields retrieved, the security requirements, and the operation's read-only status. There is zero wasted language.
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?
Given the simplicity of a zero-parameter list operation, the definition is highly complete. It specifies the source, the output data structure, and the necessary permissions, leaving the agent with all the context needed to invoke it correctly.
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?
Since the input schema has zero parameters, the baseline score of 3 is applied. The description does, however, add useful semantic value by defining the structure of the output (the specific fields listed), aiding downstream agent processing.
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 uses a specific action ('List'), a specific resource ('courses'), and provides a comprehensive list of the data points returned (LV number, title, type, semester, and lecturers). This makes its function immediately clear.
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?
The tool name and the source specified ('Eigene') imply its usage is restricted to the user's personal course list. However, it provides no explicit exclusion criteria or advice on when to choose this over a broad search tool like search_courses.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.