Skip to main content
Glama
Sign In
DB-25

arc-control-mcp

by DB-25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Reload Tab

reload_tab
Idempotent

Reload a tab and confirm the document actually changed, even for background tabs. Returns ok false if the old page is still displayed.

Instructions

Reload a tab, then confirm the document really was replaced rather than assume it. Works on a background tab. Takes wait_until_loaded and timeout_ms like the other navigating tools, and returns from, to and the tab. Fails with ok false when the tab is still showing the document that was there before, which is what a slow server or a page holding on to unload looks like from outside.

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

A4.5/5.0
Behavior5/5

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

The annotations already cover safety hints (readOnly false, idempotent, non-destructive), so the description goes further by explaining the failure mode: ok=false when the document is unchanged, and why (slow server, unload handlers). This is genuinely valuable behavioral context beyond the annotations.

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?

Three sentences, front-loaded with the primary action and verification behavior. Reasonably tight, though the final clause about 'a page holding on to unload' is slightly long despite being informative.

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?

Given the tool has no output schema, the description helpfully explains return fields (from, to, tab) and the ok=false failure condition. It's nearly complete, though it could note whether the tab_id is required for background tabs versus current.

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 coverage is 100%, so the schema already documents tab_id, timeout_ms and wait_until_loaded in detail. The description confirms which params are shared with sibling navigating tools, adding minor cross-tool context but not new parameter meaning.

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 (reload) and resource (tab) with added scope: verification that the document actually changed, and background-tab support. This distinguishes it from neighbors like wait_for_load or stop_loading without naming them directly.

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?

Implies when to use it (reloading a tab and detecting a stale document) and notes it works on a background tab. It references 'the other navigating tools' generically but doesn't name specific alternatives or explicit when-not conditions.

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