Skip to main content
Glama
Sign In
DTU Learn MCP

DTU Learn MCP

by frederikngh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List my courses

list_courses
Read-onlyIdempotent

Lists your current DTU Learn courses and their IDs so you can use the correct course number or ID with other tools. Set include_past to also show earlier semesters.

Instructions

Lists the user's DTU Learn courses (current semester by default) with their ids. Use the course number or id with the other tools.

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

Input Schema

NameRequiredDescriptionDefault
include_pastNoAlso list courses from earlier semesters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's added value is the semester default and the fact that ids are returned. It does not cover pagination or volume expectations, but for a safe read that gap is minor.

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 short sentences, with the scope (current semester) and the actionable payoff (ids for other tools) front-loaded. No wasted phrasing.

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 single optional-parameter read tool with rich annotations, the description covers what it returns and the default scope, which is essentially everything an agent needs. Only minor gaps exist around result size or pagination, which are not material here.

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%, so parameter documentation is fully handled by the schema. The phrase 'current semester by default' hints that a past-inclusive mode exists but doesn't name or explain the include_past flag beyond what the schema already says, so baseline 3 applies.

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?

States a specific verb+resource ('Lists the user's DTU Learn courses') and adds scope ('current semester by default') plus what is returned ('with their ids'). No sibling overlaps in listing courses, so the differentiation need is low, but it doesn't explicitly contrast with anything.

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

Usage Guidelines4/5

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

'Use the course number or id with the other tools' gives clear downstream context, effectively telling the agent this is the entry point for obtaining course identifiers. It implies usage but never states an explicit exclusion or alternative path.

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