Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Elegir en un desplegable de filtro

educa_select_filter
Idempotent

Selects a dropdown option by field label and option text on Educa Navarra pages, including searchable dropdowns and open dialogs, while excluding student grade-table dropdowns.

Instructions

Elige una opción en un desplegable de la página (normal o con buscador, como los de Educa-Gestión; si hay un diálogo abierto, el del diálogo) por la etiqueta o nombre del desplegable, p. ej. field="Evaluación", option="1ª Evaluación"; field="Grupo", option="2º ESO B"; field="Materia", option="Matemáticas". No toca los desplegables de nota de la tabla de alumnos (para eso está educa_fill_grades).

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": {
      "field": "<field>",
      "option": "<option>"
    },
    "name": "educa_select_filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesParte de la etiqueta, name o id del desplegable
optionYesTexto de la opción a elegir

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description focuses on useful extra behavior: it resolves the dropdown in the open dialog if one exists, matches on partial label/name, and deliberately leaves grade dropdowns untouched. It does not say what happens on failure or whether the selection is verified after clicking, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and scope, followed by the examples and the exclusion; nothing is padded. The triple example is slightly redundant (two pairs would carry the same point), but it is directly useful for a fuzzy label-matching tool.

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 two-parameter UI action with rich annotations and full schema coverage, the definition covers target selection, dialog handling, matching semantics, and the negative boundary. Only the failure/no-match behavior and any wait/retry semantics are missing, which are minor for this complexity.

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 baseline is 3; the description earns extra credit by giving three concrete field/option pairs that show the expected label wording and option text format. That reduces guessing about whether to pass a full label or a fragment, though it does not disambiguate collisions when two dropdowns share a partial label.

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?

States a specific verb and resource ('Elige una opción en un desplegable de la página') plus the resolution rule (by dropdown label/name) and scope variants (normal dropdown, searchable dropdown, dropdown inside an open dialog). It also carves out an explicit exclusion, so an agent can distinguish it from the grade-filling sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives both when-to-use and when-not-to-use: use it for page/dialog dropdowns identified by label, but not for the student table's grade dropdowns, and names the alternative tool (educa_fill_grades) for that case. The only thing left implicit is what to do when the dropdown cannot be found.

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