Skip to main content
Glama

cuestionarios

Check Moodle quizzes and exams for open/close times, deadlines, time limits, attempts used, and best grades; filter by course or availability.

Instructions

Cuestionarios/exámenes en línea: cuándo abren y cierran, tiempo límite, intentos usados y mejor nota.

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

Input Schema

NameRequiredDescriptionDefault
cursoNoId o parte del nombre del curso (opcional)
solo_disponiblesNoSolo los que están abiertos o abrirán pronto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it partially meets it by enumerating the returned fields, which signals a read-only query. It does not state the scope (enrolled courses only? past quizzes?), whether results are paginated, or any auth/permission requirements.

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 compact sentence, front-loaded with the resource and followed by the payload fields; nothing is redundant. It is slightly telegraphic in style, but no wording needs to be cut.

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?

This is a simple two-parameter, zero-required read tool with no output schema, and the description compensates for the missing output schema by naming the return fields. The remaining gap is scope/timeliness (which courses, which term), which is minor for a tool of this complexity.

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 both parameters (curso, solo_disponibles) are documented in the schema itself. The description's phrase about when quizzes open/close loosely maps to solo_disponibles but adds no matching syntax or filtering semantics beyond what the schema already says.

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 (online quizzes/exams) and enumerates exactly what it exposes: opening/closing windows, time limit, attempts used, and best grade. That is enough to distinguish it from siblings like calificaciones (grades) or listar_tareas (tasks), though the verb itself (list/show) is left implicit.

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 guidance, no exclusion of alternatives, and no prerequisites. The overlap with calificaciones ('mejor nota') is never addressed, so the agent must infer on its own when this tool is preferable to the grades tool.

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