Skip to main content
Glama
Sign In
fast-browser-mcp

fast-browser-mcp

by donleqt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fast_browser_act

Execute a browser action like click, fill, type, or press, and automatically receive updated snapshot, diff, and error information for QA testing.

Instructions

Run one browser action and automatically refresh snapshot, diff, and errors.

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": {
      "sessionId": "<sessionId>",
      "action": "<action>"
    },
    "name": "fast_browser_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
valueNo
actionYes
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool automatically refreshes snapshot, diff, and errors after the action, which is useful. However, it omits other behavioral traits such as destructiveness, authorization needs, or side effects on session state.

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 exceptionally concise with a single sentence that front-loads the core action and side effect. Every word adds value, with no redundancy.

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

Completeness2/5

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

Given the tool's complexity (4 parameters, no output schema, no annotations) and the presence of many sibling tools, the description is inadequate. It fails to explain parameter usage, return behavior, or error states, leaving the agent with insufficient information to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain parameters. It does not mention 'sessionId', 'ref', or 'value', which are critical for correct invocation. Only 'action' is implied by 'browser action', but the meaning of 'ref' and 'value' remains unclear.

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 clearly states it runs one browser action (implying click, fill, type, press from the schema) and automatically refreshes snapshot, diff, and errors, distinguishing it from sibling tools that handle those side effects separately. It lacks specificity on the exact action types but is still clear.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or contrast with sibling tools like fast_browser_state or fast_browser_report.

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