Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Leer el fichero de notas

educa_load_grades_file
Read-only

Reads an Excel or CSV grade file from your computer and returns a student-to-grade list. It auto-detects name and grade columns and does not modify Educa.

Instructions

Lee un Excel (.xlsx) o CSV del ordenador del profesor y devuelve la lista alumno → nota que se ha entendido. No toca Educa. Detecta solas las columnas tipo "Alumno"/"Apellidos"+"Nombre" y "Nota"/"Nota final"/"Calificación"; si no, indícalas.

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": {
      "file_path": "<file_path>"
    },
    "name": "educa_load_grades_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetNoHoja del Excel (por defecto la primera)
file_pathYesRuta absoluta al .xlsx o .csv
id_columnNoCabecera de una columna de identificador (NIA), opcional
name_columnNoCabecera de la columna del alumno
grade_columnNoCabecera de la columna de la nota

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real context beyond them: it never touches Educa, it auto-detects column headers with named heuristics, and it requires explicit column names as a fallback. It does not cover failure modes (unreadable file, missing header row) or whether partial/ambiguous parses are reported, which keeps it short of a 5.

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, front-loaded with the action and the 'no toca Educa' boundary, then the detection heuristics. Every sentence carries information; nothing is repeated from the schema or title.

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 five-parameter, read-only parsing tool with no output schema, the description covers input formats, the shape of the result, the side-effect boundary, and the column-detection contract. Only error/ambiguity handling is absent, a minor gap given the annotations already establish that nothing is mutated.

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 coverage is 100%, so the schema itself documents all five parameters and the baseline would be 3. The description earns the extra point by explaining the auto-detection logic that determines when name_column and grade_column must be supplied, which is behavior no schema field captures; id_column (NIA) and sheet are not discussed.

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?

The description gives a specific verb (lee), a specific resource and format (.xlsx or .csv from the teacher's machine), and states what is returned (a student → grade mapping). The clause 'No toca Educa' explicitly separates it from the sibling tools that drive the Educa web app, so an agent can pick it without opening a schema.

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 implied rather than stated: the tool is for local grade files and explicitly out of scope for Educa, and the closing 'si no, indícalas' tells the agent what to do when auto-detection fails. However, no sibling is named as an alternative (e.g. educa_read_grade_sheet for reading from Educa), so the routing decision is left partly 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