Skip to main content
Glama
Sign In
ufsc-moodle-mcp

ufsc-moodle-mcp

by jeanmartina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Listar mensagens recebidas/enviadas no Moodle

get_messages
Read-onlyIdempotent

Lists direct messages and recent notifications from a Moodle teacher account, with filters for message type, direction, read status, and result limit.

Instructions

Lista as mensagens diretas ou notificações recentes da conta do professor no Moodle.

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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTipo de mensagem: "conversations" (padrão), "notifications" ou "both".
limitNoQuantidade máxima de mensagens a retornar (padrão: 20).
directionNoDireção das mensagens: "received" (padrão) ou "sent".
readStatusNoFiltro de leitura: "all" (padrão), "unread" ou "read".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description usefully implies the results are scoped to the authenticated teacher's account (no user parameter exists), but it says nothing about ordering, pagination beyond the schema's limit, truncation, or what a message record contains.

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 front-loaded sentence that names the resource and its scope with no filler. It is efficient, though very thin for a tool with four filter parameters.

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?

This is a simple read-only listing tool with fully documented optional parameters and no output schema, so the description does not need to document return fields. Still, it omits anything about result ordering or what 'recent' means in practice, which an agent would want before calling it.

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?

Schema description coverage is 100%, including defaults and enum meanings for type, direction and readStatus, so the schema already carries parameter meaning. The description echoes the type concept ("mensagens diretas ou notificações") but adds no syntax, interaction, or default information beyond what the schema states.

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?

The description states a specific verb ("Lista") and resource ("mensagens diretas ou notificações") scoped to the teacher's Moodle account. It is clearly distinguishable from the write-oriented sibling send_message, though it does not explicitly name that sibling or the direction/read-status dimensions covered by the schema.

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?

There is no when-to-use or when-not-to-use guidance: nothing tells the agent to prefer this over get_forums, get_forum_discussions, or send_message, and no prerequisites or context are given. Only the word "recentes" hints at intended scope, so usage must be inferred entirely.

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