Skip to main content
Glama
Sign In
Educa Navarra

Educa Navarra

by vTanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cerrar el navegador

educa_close_browser
Idempotent

Closes the browser window controlled by the server, ending the active automation session; the session profile may be remembered for the next run.

Instructions

Cierra la ventana del navegador que controla el servidor. La sesión puede quedar recordada en el perfil para la próxima vez.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value by noting the session may persist in the profile for next time, which tells the agent state survives the close. It still doesn't say what happens to unsaved in-page work or whether closing twice errors, though idempotentHint partly covers the latter.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the persistence caveat.

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 zero-parameter, no-output-schema tool whose annotations already carry the safety and idempotency profile, the description covers what it does and the main side effect worth knowing. Only the behavior when no browser is running is left unstated, a minor gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The prose is silent on arguments, which is correct here.

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: closes the browser window controlled by the server. The qualifier 'que controla el servidor' usefully scopes it to the server-managed browser, so an agent can tell it apart from page-level actions like educa_navigate or educa_inspect_page without opening the schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative named. The implication that this ends the browser session is inferable from the verb, but nothing states preconditions (e.g. whether a browser must be open) or when to prefer leaving the session running.

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