Skip to main content
Glama

calificaciones

Fetch grades for a specific Moodle course by course ID or name, enabling students to review results and monitor academic progress.

Instructions

Muestra mis calificaciones de un curso (libro de calificaciones).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "curso": "<curso>"
    },
    "name": "calificaciones"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursoYesId o parte del nombre del curso

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. The possessive 'mis' usefully implies results are scoped to the authenticated user rather than arbitrary students, but nothing is said about read-only nature, whether the response covers all assignments or just a final grade, or how results are ordered.

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?

One short sentence with the resource front-loaded and no filler; the parenthetical earns its place by disambiguating 'calificaciones' as the gradebook. It is arguably slightly under-specified rather than padded.

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 one-parameter read tool with no output schema, the description covers what is retrieved but not what comes back (per-assignment scores vs. a course average) or how ambiguous course matches behave. Adequate to attempt a call, thin for interpreting the result.

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 coverage is 100% and the single 'curso' parameter already documents 'Id o parte del nombre del curso', so the schema does the heavy lifting. The description adds no meaning beyond it, such as whether a partial name match fails on ambiguity or how multiple matches are resolved.

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?

States a specific verb and resource: 'Muestra mis calificaciones de un curso', with the parenthetical 'libro de calificaciones' clarifying it is the gradebook rather than a general course view. It is distinguishable from siblings like ver_curso or listar_tareas, though it never names an alternative to reinforce the distinction.

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?

Usage is only implied: an agent can infer it should call this when it needs the user's grades for one course, since 'de un curso' signals per-course lookup. There is no explicit when-to-use statement, no prerequisites, and no mention of when another tool (e.g., ver_curso) would be preferable.

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