Skip to main content
Glama
Sign In
DTU Learn MCP

DTU Learn MCP

by frederikngh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Recent announcements

get_announcements
Read-onlyIdempotent

Retrieve recent announcements from all or selected courses, newest first, with optional days-back and course filters to check course news and updates.

Instructions

Shows recent announcements (news) from all courses, newest first.

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": "get_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to look (default 14).
courseNoCourse: a DTU course number (e.g. "02450"), part of the course name, or the Brightspace org unit id from list_courses. Omit for all courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuine behavioral fact — results are ordered newest first — but says nothing about result limits, pagination, or what happens when days exceeds available history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the ordering constraint front-loaded; no wasted words. It loses a point because "from all courses" is a slightly misleading framing given the course filter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple read tool with full annotation coverage, but with no output schema the description never hints at what an announcement record contains (title, body, timestamp, course), leaving the agent to discover the return shape empirically.

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% and both parameters are documented with examples, so the schema does the heavy lifting. The description adds only the "all courses" default, which is already implied by the course param's "Omit for all courses" text.

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 and resource ("Shows recent announcements") plus ordering ("newest first"), so the agent knows exactly what it returns. It fails to distinguish itself from the sibling get_upcoming, and the phrase "from all courses" sits awkwardly against the existence of a course filter.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over get_upcoming or other course-activity tools, and no mention of prerequisites such as needing to be logged in. Usage must be inferred entirely from the name.

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