Skip to main content
Glama

local-mcp

by com.local-mcp

Web Navigate

web_navigate

Navigates a web session to a URL (using its saved login if any) and returns the resulting URL + page title. Opens the session if it doesn't exist. CHECK loaded before reading: when it is false the page did not load and message says why — reading the session then describes a blank document, not the site. Read the page with web_read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to open (https).
sessionNoSession name (default 'default').
timeout_secondsNoMax seconds to wait for load (default 25).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue only when the requested page actually loaded.
urlNoThe URL the browser settled on (redirects followed). If it isn't the page you asked for, the navigation didn't deliver it.
errorNoPresent only on failure: nav_failed (the browser rejected the load), nav_timeout, or nav_blank (it finished on a blank document).
titleNoThe resulting page title.
loadedNoTrue only when the browser ended on a real web page. False means nothing was loaded — do NOT read the session and treat the result as page content.
messageNoPresent only on failure: why the page didn't load, and what to do about it.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, the description discloses that the session is opened if absent, that saved logins are used, that the tool returns URL plus title, and specifically explains the `loaded` flag failure mode and its consequence for subsequent reads. This is substantial behavioral context that annotations alone would not provide.

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?

The description is three sentences, front-loaded with the primary action, and then provides essential caveats in compact form. Every sentence adds new information: what the tool does, session/lifecycle behavior, and why checking `loaded` matters.

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?

For a navigation tool with one required parameter and an output schema, the description covers the core return value, session creation, saved-login behavior, failure indication, and the proper follow-up tool. It is complete enough for an agent to use it correctly without additional context.

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?

The input schema already has 100% coverage with descriptions for url, session, and timeout_seconds. The tool description adds contextual behavior around session opening and loading state but does not add parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Navigates a web session to a URL' and clearly states the return value ('resulting URL + page title'). It distinguishes itself from sibling tools like web_read by explicitly positioning navigation as the action and reading as a separate step.

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?

The description gives clear usage context: navigate to a URL, then 'Read the page with web_read.' It also provides an important conditional instruction: 'CHECK `loaded` before reading,' telling the agent when to avoid reading a blank document. It does not enumerate when not to use the tool versus other web tools, but the guidance is sufficient for common use.

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

All local-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Resources