easy-ui-mcp

Overview Schema Source Related Servers Discussions Admin

ui_navigate_history

ui_navigate_history

Move back or forward through browser history or reload the current page while preserving history, then report the resulting URL and title to confirm state survives a reload.

Instructions

Go back or forward in the browser history, or reload the current page, and report the resulting URL and title. Unlike ui_navigate this keeps the history, so it can check that state survives a reload. Going back or forward with no such history entry is an error that says so.

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": {
      "action": "<action>"
    },
    "name": "ui_navigate_history"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	back, forward, or reload
`session_id`	No	Which open session to act on, as returned by ui_start_session. Optional with one open session; required when several are open.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations the description carries the full burden and does reasonably well: it discloses the return values (URL and title) and the error condition for navigating past the ends of history. It does not discuss side effects such as losing unsaved page state on reload or any impact on the open session, which is the remaining gap.

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 tight sentences: capability and return value first, sibling differentiation second, error semantics last. Nothing is repeated and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Only two parameters, both fully described in the schema, and no output schema, yet the description tells the agent what comes back (URL and title). Combined with the error condition and sibling differentiation, an agent has everything needed to invoke it correctly.

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 coverage is 100% and the action enum with its three values plus session_id semantics are fully documented in the schema. The description's only added meaning is the error behavior tied to back/forward, so it neither compensates for nor is required to compensate for anything.

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 set (back/forward/reload) over a specific resource (browser history / current page) and also what it returns (resulting URL and title). It names ui_navigate as the contrasting sibling, so an agent can distinguish the two 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 Guidelines5/5

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

Explicitly names the alternative (ui_navigate) and the condition that selects this tool instead: it keeps history, so it can verify state survives a reload. It also states the failure case when there is no such history entry, which is exactly the edge case an agent needs to anticipate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.