Skip to main content
Glama
Sign In
moodle-mcp

moodle-mcp

by ralstonraphael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

moodle_announcements

Read-only

Retrieve recent posts from Moodle course Announcements forums, optionally filtered by course IDs, ordered by date, to catch important updates.

Instructions

Latest posts in each course's Announcements forum, 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": "moodle_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idsNo
per_courseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful ordering ('newest first') and per-course scoping, but omits key behavior: what happens when course_ids is omitted, and how per_course limits results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the ordering fact front-loaded and no filler. It is arguably too terse for a two-parameter tool, but every word earns its place.

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?

For a simple read-only list tool with no output schema, the description conveys the essential purpose, but with 0% schema coverage and no annotation detail on defaults, it leaves the parameter behavior unexplained. Adequate but with a clear gap.

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?

Schema description coverage is 0%, so the description carries the full burden for both parameters — yet it never mentions course_ids or per_course. An agent cannot tell from the text that course_ids=null covers all courses or that per_course defaults to 5.

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?

Names a specific resource (each course's Announcements forum) and the returned items (latest posts), which distinguishes it from moodle_discussion and moodle_search without opening schemas. It stops short of explicitly contrasting with those siblings, but the scope is unambiguous.

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?

No when-to-use guidance and no named alternative, even though moodle_discussion, moodle_search, and moodle_notifications are obvious competing sources for course posts. Usage is only implied by the resource named.

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