Skip to main content
Glama
Sign In
DTU Learn MCP

DTU Learn MCP

by frederikngh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Content item details

get_topic
Read-onlyIdempotent

Retrieve details for a single course content item by topic ID—including description, dates, and URLs for links, videos, and external tools like Panopto.

Instructions

Shows details for one content item (topicId from get_course_outline): description, dates, and the URL for links, videos and external tools such as Panopto. Use read_file instead to read the contents of a file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course": "<course>",
      "topic_id": "<topic_id>"
    },
    "name": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYesCourse: a DTU course number (e.g. "02450"), part of the course name, or the Brightspace org unit id from list_courses.
topic_idYestopicId from get_course_outline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: it discloses that the payload includes externally-hosted resource URLs (Panopto-style tools), which explains the openWorldHint and matters for how an agent uses the result.

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 sentences, zero filler, and the core purpose plus return fields are front-loaded before the read_file exclusion. Nothing to trim.

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?

With no output schema, the description carries the burden of describing returns, and it does so at a useful level of detail (fields plus URL-bearing resource types). Only gap is that it does not say what the object looks like structurally or how external-tool entries differ from links.

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 both parameters are already documented (including that topic_id comes from get_course_outline). The description's restatement of that provenance adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb + resource ("Shows details for one content item") with an explicit enumeration of what comes back: description, dates, and URLs for links/videos/external tools. It also names the sibling it is not (read_file), so an agent can discriminate without opening schemas.

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?

Provides a clear when-not rule: "Use read_file instead to read the contents of a file," plus the provenance hint that topicId comes from get_course_outline. It stops short of distinguishing this from get_assignment for topics that are assignments, so routing against every sibling is not fully covered.

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