Skip to main content
Glama
Sign In
DB-25

arc-control-mcp

by DB-25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Go Forward

go_forward

Navigate a specified Arc tab forward in browser history, then confirm the page actually moved before reporting success. Use it to step forward after going back.

Instructions

Navigate a tab forward in history. Goes through the page and confirms the tab really moved before reporting success.

Input Schema

NameRequiredDescriptionDefault
tab_idNoArc tab id from list_tabs. Omit to use this agent's current tab. A tool that changes a tab will not fall back to the tab the user is looking at, so pass this or call open_url first.
timeout_msNoHow long to wait for loading. Capped at 30000ms so the call cannot outlive a client's request timeout. To wait longer, call this again.
wait_until_loadedNoWait for the page to finish loading before returning

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / properties / tab_id / description
      Previous value: -"Arc tab id from list_tabs. Omit to use this agent's current tab, falling back to whatever tab is active in Arc."New value: +"Arc tab id from list_tabs. Omit to use this agent's current tab. A tool that changes a tab will not fall back to the tab the user is looking at, so pass this or call open_url first."
    • changedInput schema / properties / timeout_ms / description
      Previous value: -"How long to wait for loading. Capped at 30000ms, because a longer call is killed by the client before it can answer. To wait longer, call wait_for_load again: repeated short waits each hand back a real readyState and url, which one long wait does not."New value: +"How long to wait for loading. Capped at 30000ms so the call cannot outlive a client's request timeout. To wait longer, call this again."
  2. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description nonetheless adds a real behavioral trait: it verifies the tab actually moved before reporting success, which tells the agent the return is a confirmed result rather than an optimistic ack.

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 sentences, zero filler, action front-loaded. It could be marginally tighter, but nothing is wasted.

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 simple navigation action with a fully documented schema and clear annotations, the description covers what the tool does and how success is determined. With no output schema, a brief note on failure behavior (e.g., no forward entry) would close the last gap.

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 description coverage is 100% and the schema already explains tab_id fallback behavior, the timeout cap, and wait_until_loaded. The description adds no parameter meaning beyond that, so it sits at the baseline.

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+resource ('Navigate a tab forward in history'), which cleanly distinguishes it from siblings like go_back, reload_tab, and open_url. An agent can select it 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 Guidelines3/5

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

Usage is implied by 'forward in history', but the description never names go_back as the counterpart or states when not to use it (e.g., no forward entry available). The tab_id schema description carries the 'pass this or call open_url first' guidance, so routing context exists but outside the description.

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