Skip to main content
Glama
Sign In
utn-mcp

utn-mcp

by nialvape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aula_grades

Read-only

Retrieve your course grades, including quizzes, assignments, and manually uploaded marks, to check your progress or whether you passed a subject.

Instructions

Las calificaciones del usuario en un curso, las mismas que ve en "Calificaciones" del aula: tareas, cuestionarios y también las notas que el docente carga a mano (un TP corregido en papel, un parcial), que no aparecen en ningún módulo. Usala para saber cómo va en una materia o si aprobó algo.

Cada ítem trae calificacion (como la formatea el aula, sin nota si todavía no hay), maximo, porcentaje y, si es de un módulo, su direccion para abrirlo con aula_open. tipo dice de dónde sale: el módulo (quiz, assign), "manual", "category" o "course" (el total).

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": {
      "direccion": "<direccion>"
    },
    "name": "aula_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
direccionYesDirección del curso, de aula_list_courses. Ej: "/curso/691".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a read-only, closed-world call, so safety needs no restating. The description instead discloses the item shape an agent will actually reason over: calificacion may be absent when not yet graded, plus maximo, porcentaje, direccion and the tipo taxonomy (quiz/assign/manual/category/course). That is real behavioral value beyond the annotations, short only of pagination or ordering details.

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?

Front-loaded with the purpose sentence, then a second paragraph that earns its space by describing the return fields that no output schema covers. Dense but free of filler; the length is justified by the missing output schema rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one parameter, high schema coverage and no output schema, the definition covers everything an agent needs: what it returns, how to interpret missing grades, how tipo maps to module or manual origin, how to follow direccion, and where the input address comes from. Nothing material is left unspecified.

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 direccion parameter is already documented with its format and source, so the description cannot add much. It does reinforce the provenance (from aula_list_courses) but most of its parameter-adjacent text describes the output direccion rather than the input, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (the user's grades in a course) and pins the scope precisely, including the non-obvious detail that manually uploaded grades (corrected TPs, parciales) are included even though they don't appear in any module. That contrast implicitly separates it from the module-oriented siblings, so an agent can tell what this retrieves without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States a use case ('saber cómo va en una materia o si aprobó algo') and chains correctly to aula_list_courses for the input direccion and to aula_open for any item carrying a direccion. No explicit exclusions or named alternatives for the 'grades of one item' case, which keeps it below a 5.

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