Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_assignments

Retrieve a course's assignments with instructions, deadlines, and attachments, and get assignment IDs to check submission status.

Instructions

List the assignments of one course (id from list_courses) with instructions, deadlines and attachments. The assignment_id values feed get_assignment_status.

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_id": "<course_id>"
    },
    "name": "list_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results include instructions, deadlines, and attachments, and that assignment IDs feed another tool, but it does not cover permissions, ordering, pagination, or other operational behavior.

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 definition is two sentences, front-loaded with the main action and scope. Every phrase adds useful information about return content or tool relationships.

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?

For a simple one-parameter list tool with no annotations and no output schema, the description gives enough context to call it correctly and to know what it returns. It could be slightly more complete with notes on ordering or whether empty results are expected, but no major gap blocks correct invocation.

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?

There is only one parameter, course_id, and the schema provides 0% description coverage. The description compensates by explaining that the ID should come from list_courses, which is meaningful provenance for an otherwise plain integer parameter.

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 names a specific verb and resource: list assignments for one course. It also clarifies scope with 'one course' and identifies relevant sibling relationships: course IDs come from list_courses and assignment IDs feed get_assignment_status.

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?

It gives clear usage context by stating the course ID comes from list_courses and that the resulting assignment IDs are used with get_assignment_status. It does not explicitly state when to avoid this tool versus get_course_contents or list_deadlines, so it stops short of full when/when-not guidance.

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