Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_notifications

Retrieve recent Moodle notifications, including forum posts, submission confirmations, and grades, with unread counts and newest items first.

Instructions

Return the user's latest Moodle notifications (new forum posts, submission confirmations, grades) with the unread count, 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_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral burden, and it does add useful detail: results are newest-first and include the unread count. However, it doesn't say what happens if there is no session, whether results pages or truncate, or how the unread count interacts with the limit.

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?

One sentence, front-loaded with the action and resource, with the ordering and unread-count details packed compactly into the same sentence. No wasted words.

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?

With no output schema and no annotations, the description helpfully characterizes the return: a notification list, newest first, with an unread count. Only the limit behavior and any authentication requirement are missing, which keeps it short of a 5.

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?

The single parameter, limit, has zero schema description coverage and is never mentioned in the description. The agent must guess whether limit caps the list length, affects the unread count, or defaults to 20. The description does not compensate for the 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?

A clear verb and resource ('Return the user's latest Moodle notifications') plus concrete examples of what counts as a notification (forum posts, submission confirmations, grades). It doesn't need to distinguish itself from siblings like get_grades or get_forum_discussions because it is a distinct aggregate feed, though it never says so explicitly.

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 read-only nature of fetching a notification feed makes the usage clear by implication, but there is no explicit statement of when to use this tool versus get_recent_changes or get_grades, and no mention of prerequisites such as authentication as the current user.

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