Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ir a una URL de Educa

educa_navigate
Read-only

Opens a specific Educa Navarra URL in the browser, restricted to allowed domains such as educa.navarra.es. Use it to go directly to portal pages; navigate menus with click actions.

Instructions

Abre una URL concreta de Educa en el navegador. Solo se permiten los dominios de allowedHosts (por defecto educa.navarra.es). Para moverse por menús es mejor educa_click.

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": {
      "url": "<url>"
    },
    "name": "educa_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL completa, p. ej. https://educa.navarra.es/...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/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, so the safety profile is covered. The description adds a genuinely useful behavioral constraint not present in the structured fields: only allowedHosts domains (default educa.navarra.es) can be opened. It stops short of describing what happens on a blocked host or whether it waits for page load.

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, each earning its place: what it does, the hard constraint, and the sibling routing hint. The most decision-relevant content comes first, with no padding or redundancy.

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 one-parameter navigation tool with full schema coverage and annotations covering safety, this is essentially complete, and no output schema means return values need no explanation. The only minor gap is unspecified behavior on a non-allowed host or on navigation failure.

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% and the single parameter is already documented as a full URL with an example. The description adds meaning beyond the schema by constraining the permitted host domains, which the schema itself does not enforce or mention.

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 states a concrete verb and resource ("Abre una URL concreta de Educa en el navegador") and immediately scopes it with the allowed-hosts restriction. It also names the sibling educa_click and the condition that selects it, so an agent can separate navigation-by-URL from navigation-by-menu 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?

It gives explicit routing guidance: use educa_click for moving through menus, implying navigate is for direct URL jumps. The host allowlist implicitly says when not to use it (external or non-listed domains), though the failure behavior for a disallowed host is left unstated.

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