Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ver la estructura HTML

educa_dump_html
Read-only

Returns simplified HTML from all frames or the open dialog, stripping scripts and styles while keeping useful attributes to understand forms and locate CSS selectors without modifying the page.

Instructions

Devuelve el HTML simplificado de la página actual (sin scripts ni estilos, solo atributos útiles: id, name, class, role, formcontrolname...), de todos los marcos. Si hay un diálogo abierto, solo el diálogo. Úsala cuando educa_inspect_page no basta para entender un formulario o para averiguar selectores CSS para educa_click o la configuración. No cambia nada.

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_dump_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoSelector CSS de la zona a mostrar (por defecto el diálogo abierto o toda la página)
max_charsNoTamaño máximo por marco
frame_url_containsNoSolo los marcos cuya URL contenga este texto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and 'No cambia nada' is consistent with them. Beyond that, the description discloses substantive behavior the annotations don't: scripts and styles are stripped, only useful attributes (id, name, class, role, formcontrolname) survive, and an open dialog replaces the page in the output. It doesn't mention truncation or per-frame size limits, which is why it isn't 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 what is returned, then the frame/dialog scoping rule, then the usage trigger, then the safety note. Three sentences with no filler; the attribute list is long but that list is genuinely informative.

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 describing the shape of the return value is essential, and the description does that (simplified HTML, useful attributes only, dialog-only case, all frames). What remains thin is how frames are delivered and how truncated output is marked, which the schema's max_chars default only partially covers.

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 all three parameters are already documented in the schema, including the selector default (open dialog or whole page) and per-frame size limit. The description's note that output covers 'todos los marcos' and only the dialog when present reinforces the defaults but adds no new syntax or constraint beyond the schema.

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 ('Devuelve el HTML simplificado') plus the exact scope: all frames, or only the open dialog. It also names the sibling it complements (educa_inspect_page), so an agent can tell the two apart without opening either 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?

Gives a clear trigger ('cuando educa_inspect_page no basta para entender un formulario') and downstream consumers (educa_click, la configuración). It stops short of an explicit when-not rule or other alternatives such as educa_screenshot, but the context for choosing it is unambiguous.

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