Skip to main content
Glama

browser_action_status

Retrieve metadata for a failed browser command by operation ID without replaying it; inspect the page before retrying because a completed reply does not confirm persistence.

Instructions

Recover metadata for an operation ID from a failed command without replaying it. A completed reply does not prove website persistence; inspect the page before any retry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operationId": "<operationId>"
    },
    "name": "browser_action_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose that the tool does not replay the operation and that a completed reply does not prove persistence, but it omits whether the lookup is read-only, whether it requires an active browser session, and how it behaves for unknown or expired IDs.

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?

Two sentences, both front-loaded and free of filler. The core action comes first and the caution about retrying follows as a distinct, purposeful clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema recovery tool the description covers the essential caution but leaves the return content ('metadata' is undefined) and failure modes unstated. An agent knows when to call it but not exactly what it will receive.

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 0% for the single operationId parameter; only a regex pattern is given. The description implies the ID originates from a failed command, which helps an agent source the value, but it does not explain the ID's format, lifetime, or validity constraints beyond the schema pattern.

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?

States a specific verb and resource ('Recover metadata for an operation ID') and adds a scoping clause ('from a failed command without replaying it') that separates it from any replay/retry behavior. It does not name a specific sibling, but the recovery-of-metadata framing is distinctive enough that an agent can identify the tool's role.

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?

Gives clear situational context: use it after a failed command, and inspect the page before retrying. The when-to-use trigger (failed operation, pre-retry) is explicit, though no when-not conditions or named alternatives are given.

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