Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_courses

Retrieves a student's enrolled eNauczanie courses, including IDs, names, and end dates; optionally includes hidden courses to clarify available course access.

Instructions

List the user's enrolled courses on eNauczanie. Returns id, shortname, fullname and end_date.

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

Input Schema

NameRequiredDescriptionDefault
include_hiddenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about permissions/auth requirements, pagination, ordering, or what include_hidden changes in the result. It only names return fields, which is largely redundant with the output schema and is not the behavioral context a caller needs.

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 short sentences, front-loaded with the scope and followed by the return shape, with no filler.

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?

The tool is simple and an output schema exists, so return-value explanation is not strictly needed. However, the sole optional parameter is left unexplained and no context is given about the user/auth scope or result ordering, leaving a material gap for a tool with zero annotations.

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

Parameters2/5

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

There is one parameter (include_hidden) with 0% schema description coverage, and the description never mentions it at all. A caller cannot tell from the definition whether hidden/unpublished courses are excluded by default or what the flag toggles, so the description fails to compensate for the coverage gap.

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+resource (list enrolled courses) scoped to the user and to the eNauczanie platform, which clearly separates it from siblings like get_course_contents or list_assignments. It never names an alternative, so it falls short of a 5.

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?

The description gives no explicit when-to-use or when-not-to-use guidance and does not reference any sibling tool. The reader must infer that this is the entry point whose IDs feed the other course tools.

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