Skip to main content
Glama

NTNU Courses (unofficial)

by io.github.MartinSA04

get_course_info

Everything about an NTNU course except exam logistics: credits, level, campus, language of instruction, prerequisites, mandatory activities, course content / learning outcomes, credit reductions ('studiepoengreduksjon'), which study programs the teaching is planned for, contacts, and any alert notices (e.g. 'no longer taught'). English text by default; pass language 'nb' for Norwegian. Omit year for the current study year. For exam dates, times, aid codes, and rooms use get_exam_info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
languageNo
course_codeYes

TDQS

A4.7/5.0
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It discloses default language behavior, the effect of omitting year, and the scope of returned data. It does not mention permissions or side effects, which are minimal for a read operation, but still provides strong transparency.

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?

The description is concise yet comprehensive—two substantive sentences plus a clear pointer to sibling. Key information is front-loaded, and every sentence adds value.

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?

Given the rich data returned and no output schema, the description is impressively complete, listing many field categories and edge cases (alert notices). It could mention course_code format, but the current detail is still high.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates fully: it explains language as English by default with 'nb' option, year as current if omitted, and course_code as required. This adds essential meaning beyond the schema.

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?

The description specifically lists all fields returned (credits, level, campus, etc.) and explicitly states what is excluded (exam logistics). It distinguishes itself from sibling tool get_exam_info, making the purpose unmistakable.

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?

The description provides clear when-to-use (getting course details) and when-to-use-alternative (exam info → get_exam_info). It also gives practical tips on language and year parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NTNU Courses (unofficial) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct aspect of NTNU course data: scheduling, exams, grades, comparisons, search, etc. Overlaps like get_course_schedule and get_weekly_timetable are clearly differentiated by granularity, with descriptions guiding usage.

Naming Consistency5/5

All tools follow a verb_noun pattern in snake_case, using simple verbs like 'get', 'search', 'check', and 'compare'. The naming is uniform and predictable across all 12 tools.

Tool Count5/5

12 tools is well-scoped for an informational server covering courses, schedules, exams, grades, study plans, and search. Each tool serves a clear purpose without unnecessary redundancy.

Completeness4/5

The tool set covers core CRUD-like operations for course data, including search, info retrieval, scheduling, exams, grades, and study plans. Minor gaps exist, such as no dedicated tool for study program details or room information, but overall the surface is comprehensive for the domain.

Resources