Skip to main content
Glama
Sign In
DTU Learn MCP

DTU Learn MCP

by frederikngh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sign in to DTU Learn

login
Read-onlyIdempotent

Authenticates the user to DTU Learn when other tools report no active session, opening a browser window for DTU credentials and MFA unless a saved password enables automatic sign-in.

Instructions

Signs in to DTU Learn. Only call this when other tools say the user is not signed in. If the user turned on automatic sign-in (saved password) this happens without a window; otherwise it opens a browser window on the user's computer where they sign in themselves (DTU login + MFA), so tell the user to look for it. Waits up to 5 minutes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the call may open a browser window on the user's machine, requires DTU login plus MFA, may complete silently with a saved password, and blocks for up to 5 minutes. The instruction to tell the user to look for the window is critical operational context an agent could not infer from readOnlyHint/idempotentHint alone.

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?

Four tight sentences, each carrying distinct information: what it does, when to call it, what the user will see, and how long it takes. The precondition is front-loaded immediately after the purpose statement.

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

Completeness5/5

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

With no parameters and no output schema, the description supplies everything needed to call it correctly: the guard condition, the two possible execution paths, the user-facing side effect, and the timeout. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to document and the baseline applies. The description correctly spends no space on parameter details and instead covers timing and user interaction, which is the right trade-off.

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?

States a specific verb and resource ('Signs in to DTU Learn') that is unambiguous and inherently distinct from the data-reading siblings (list_courses, get_assignment, etc.). An agent can identify it as the authentication tool without inspecting any schema.

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

Usage Guidelines5/5

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

Explicitly gives the trigger condition: 'Only call this when other tools say the user is not signed in,' which wires it directly to the sibling 'status' tool's output. It also distinguishes the two execution modes (automatic vs. interactive) so the agent knows what to expect in each case.

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