Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Leer la tabla de notas

educa_read_grade_sheet
Read-only

Reads the open grade table in Educa Navarra to show each student’s current grade without changing it, and lists editable columns when multiple exist.

Instructions

Lee la tabla de calificaciones abierta en Educa: alumnos y nota actual de cada uno. No cambia nada. Si la tabla tiene varias columnas editables (p. ej. nota y observaciones, o varias evaluaciones), indica cuál con column; la respuesta lista las columnas editables.

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

Input Schema

NameRequiredDescriptionDefault
columnNoParte del texto de la cabecera de la columna de nota, p. ej. 'Final' o '1ª Ev'
response_formatNo'markdown' para leerlo, 'json' para datos estructuradosmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true; the description reinforces this with 'No cambia nada' and adds the meaningful disclosure that the response enumerates the editable columns. It does not cover error cases (e.g. no grade sheet open), but it adds real behavioral context beyond the annotations.

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?

Three short sentences with the core action front-loaded, then the non-mutation guarantee, then the parameter rule. No redundant or filler wording.

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?

There is no output schema, so the description usefully compensates by saying the response lists editable columns alongside students and grades. Parameters are fully covered by the schema. Only the behavior when no sheet is open or when the column matches nothing is unaddressed.

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%, so both parameters are already documented in the schema and the baseline of 3 applies. The description adds a little value by explaining the practical condition under which 'column' should be supplied, but nothing about format, defaults or matching behavior 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?

States a specific verb and resource (read the grade sheet open in Educa) plus what it returns: students and each one's current grade. It also implies the read/write boundary with 'No cambia nada', which distinguishes it from the fill/save siblings, though it never names an alternative explicitly.

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?

Provides a real conditional rule for the optional parameter ('if the table has several editable columns, indicate which with column'), which is genuine when-to-use guidance. However, it gives no guidance on when to choose this tool over siblings like educa_dump_html, educa_inspect_page or educa_preview_grades, so tool selection is left to inference.

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