Skip to main content
Glama

Robot Actions — Remote Device Control

by com.robotactions.test
OverviewDiscussionsAdmin

webpage_reload

Reload the page open in the device browser (CDP Page.reload) — works on BOTH iOS Safari and Android Chrome. Confirms the document was actually replaced rather than trusting the protocol ack: a sentinel is written to window before the reload and the call only reports reloaded:true once it is gone. Returns the post-reload url, and reloaded:false with a reason when the document survived, so a reload that quietly did nothing cannot read as success. Also waits for the NEW document to finish loading and reports ready, so the page is drivable when the call returns. This is the state-reset primitive between test cases on iOS, where tabs cannot be opened or closed — and unlike a same-hash navigate it forces a real load, which an SPA router would otherwise skip, leaving stale dialogs and form state behind. Pass hard:true to bypass the HTTP cache.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardNoBypass the HTTP cache (CDP ignoreCache) — a from-network reload (default: false)
udidYesDevice UDID / serial (iOS or Android)
pageIdNoTarget page/tab id — auto-picked when omitted
socketNoAndroid only: abstract unix socket name (default: chrome_devtools_remote)
platformVersionNoIgnored (kept for compatibility)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hard
      Added value: +{
+  "description": "Bypass the HTTP cache (CDP ignoreCache) — a from-network reload (default: false)",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden and does so thoroughly. It reveals the sentinel verification mechanism, the fact it does not trust the protocol ack, that it waits for the new document to load, and the exact success/failure reporting semantics (reloaded:true, reloaded:false with reason, post-reload url, ready). This is far beyond what structural data provides.

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 long but every sentence earns its place: core action, platform scope, behavioral verification, return semantics, waiting behavior, use case, and cache-bypass option. It is front-loaded and logically ordered, with no filler or redundant restatement of the tool name.

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 reload tool with no output schema, the description is remarkably complete. It explains what the caller receives (url, reloaded, reason, ready), the verification approach, the use case, and the hard parameter. An agent has enough information to invoke it correctly and interpret results without needing 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?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds no new parameter-specific meaning beyond what the schema states (e.g., hard:true bypasses cache, pageId auto-picked when omitted). It reinforces some semantics but does not compensate beyond the baseline for high schema coverage.

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: 'Reload the page open in the device browser (CDP Page.reload)'. It immediately clarifies the platform scope ('iOS Safari and Android Chrome') and later positions it as a 'state-reset primitive', distinguishing it from navigation siblings like webpage_back, webpage_forward, and web_reload. The purpose is unambiguous and well-differentiated.

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 a clear when-to-use context: 'state-reset primitive between test cases on iOS, where tabs cannot be opened or closed'. It also contrasts with a same-hash navigate, explaining why this tool forces a real load that an SPA router would skip. However, it does not explicitly exclude desktop alternatives like web_reload or playwright_reload, though the 'device browser' scope is implied.

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

All Robot Actions — Remote Device Control toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources