Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_recent_changes

Lists recent changes across your current courses by module, including announcements, files, submissions, and grades from a chosen number of days, newest first.

Instructions

List what changed in the user's current courses in the last days (new announcements and posts, new or changed files, assignment submissions and grades), per module, newest first.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden; it does disclose useful behavior — aggregation across modules, newest-first ordering, and that only the current user's courses are in scope. It does not cover whether results are capped, how large a window is practical, or that it is purely read-only (implied by 'List').

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?

A single sentence that front-loads the action and scope, then parenthetically enumerates coverage. No filler; every clause adds information.

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 one-parameter read tool with no output schema, the description supplies the return-content inventory and ordering, which is what an agent needs to decide and to interpret results. The remaining gap is the undocumented default/limits on the 'days' window.

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?

Only one parameter ('days') with 0% schema description coverage, so the description must compensate. It does explain the parameter's meaning ('last days'), but omits the schema default of 7 and any bounds or format guidance for the window.

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?

Specific verb ('List what changed') plus scoped resource ('the user's current courses') plus an explicit enumeration of the change types covered (announcements, posts, files, submissions, grades). An agent can distinguish this aggregate 'what's new' tool from siblings like get_course_contents or get_notifications without opening 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 Guidelines3/5

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

The phrase 'in the last days' and the per-module/newest-first framing imply a recent-activity digest use case, but the description never states when to prefer this over get_notifications, get_course_contents, or list_deadlines. Usage is inferable rather than explicit.

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