Skip to main content
Glama
Sign In
DTU Learn MCP

DTU Learn MCP

by frederikngh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Assignment details

get_assignment
Read-onlyIdempotent

Retrieves an assignment's full instructions, attached files, links, rubric, and your submissions with feedback so you can review requirements and results.

Instructions

Shows an assignment's full instructions, attached files (with fileIds for read_file), links, rubric names, and the user's own submissions (with submissionFileIds for read_file) and feedback, including feedback files (with feedbackFileIds for read_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>",
      "assignment_id": "<assignment_id>"
    },
    "name": "get_assignment"
  }
}

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.
assignment_idYesassignmentId from list_assignments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 safety is covered. The description adds real behavioral context beyond that: it discloses that only 'the user's own submissions' are returned (a visibility scoping rule) and that returned fileIds are intended to be passed to read_file, establishing a chaining workflow.

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 tightly-packed sentence that front-loads the return contents, with no filler. It is dense and list-like but every clause names a distinct piece of returned data, so nothing is wasteful.

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 thoroughly by enumerating each returned field group including the fileId handles for read_file. Minor gaps remain on submission scoping (e.g. group vs individual) and result size, but the agent has enough to invoke it correctly.

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% and both parameters are documented in the schema (course formats, assignment_id provenance). The description adds no parameter-level detail such as how 'course' matching behaves when a partial name matches multiple courses, so the 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 ('Shows') and resource ('an assignment') and then enumerates exactly what the detail view contains: instructions, attached files, links, rubric names, submissions and feedback. This clearly reads as the single-assignment detail fetch rather than the list_assignments sibling, though it never names the sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: you must already have an assignment_id (presumably from list_assignments) and a course. The description does not say when to prefer this over get_course_outline or list_assignments, and states no prerequisites or exclusions.

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