Skip to main content
Glama
Moodle MCP (Aula USM)

Moodle MCP (Aula USM)

by muitomou

ver_notas

Read-only

Retrieve final grades for all courses or detailed evaluation grades, ranges, percentages, and comments for a specific course.

Instructions

Notas. Sin ramo: nota final de cada ramo. Con ramo: cada evaluación con nota, rango, % y comentarios.

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

Input Schema

NameRequiredDescriptionDefault
ramoNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the mode-dependent shape of the result (aggregate final grade vs per-assessment detail with range, percentage and comments), which is genuinely useful context, but an output schema exists and no further behavioral traits (auth, caching, empty-state handling) are disclosed.

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?

Two short clauses, front-loaded with the resource and then split cleanly by parameter presence. No filler, no repetition of the tool name, and the conditional structure mirrors how an agent reasons about the optional argument.

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 single optional-parameter read tool with an output schema and read-only annotations, the description covers what is needed to call it correctly in both modes. Only the identifier format for 'ramo' and the empty-result behavior are left unstated, which are minor given the output schema.

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?

Schema description coverage is 0%, so the description must carry the meaning of 'ramo' — and it does, defining the null case as 'final grade per course' and the populated case as 'per-assessment detail'. That is a clear semantic contract beyond the bare string type, though it does not say what format the course identifier takes.

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 names the resource (grades) and specifies two distinct behaviors: without 'ramo' it returns the final grade per course, with 'ramo' it returns each assessment with grade, range, percentage and comments. An agent can tell what it retrieves, though the verb is only implied by the tool name rather than stated in the description.

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?

It effectively explains the two usage modes driven by the optional 'ramo' argument, which is the main decision an agent faces here. However, it never names an alternative sibling (e.g. ver_tarea for pending work) or states when this tool is not appropriate, so guidance stops at the parameter split.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.