Skip to main content
Glama

Go to a page

cotlet_browser_navigate
Read-only

Opens url in the current tab, or goes history back or forward. Answers the page after it: the elements and text in view, with the same numbers.

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": "cotlet_browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
tabNoThe Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.
urlNoA public http or https address, e.g. https://example.com.
dialogNoHow to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
historyNoInstead of `url`.
dialog_textNoText for a prompt dialog this step opens; implies accept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tab
      Added value: +{
      +  "description": "The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a non-destructive, non-idempotent, open-world read step, so the safety profile is given. The description adds genuinely useful behavior beyond that: it answers with the resulting page state ("the elements and text in view, with the same numbers") and implicitly signals a fresh observation after each navigation. It does not say what happens on load failure, timeouts, or blocked navigation, which matters for a non-idempotent step.

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?

Two short, front-loaded sentences with no filler; the action comes first and the return behavior second. The closing clause is slightly cryptic out of context but still earns its place by describing the answer shape.

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 six-parameter, zero-required tool with a fully documented schema and no output schema, this covers the essentials: what it acts on, the tab-guard behavior, and what the response contains. Remaining gaps (load-failure handling, whether it waits for the page to settle) are modest but real for a navigation step.

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 description coverage is 100%, so the baseline is 3, and the description does add one thing beyond the schema by framing `history` as an alternative to `url` rather than a companion. The phrase "the same numbers" hints that returned element identifiers stay stable across navigations, which is a useful interpretive cue not spelled out in the schema.

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?

The description gives a specific verb and resource ("Opens `url` in the current tab") plus the secondary mode ("goes `history` back or forward"), which is enough to tell it apart from sibling navigation tools in practice. It stops short of naming the sibling it is not, but the scope (current tab, not a new tab) is stated explicitly.

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

Usage Guidelines3/5

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

The mutual exclusivity of `url` and `history` is implied ("or"), and the `tab` parameter explanation supplies a concrete condition ("Leave it out to act on the shown tab"). However, there is no explicit guidance about when to prefer this over alternatives such as a tab-opening or page-reading sibling, and no statement of preconditions like wait behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources