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

fast-browser-mcp

by donleqt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fast_browser_state

Return a compact session QA state from files and recent timeline to preserve context for multi-step browser automation tasks.

Instructions

Return compact session QA state from files and recent timeline.

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>"
    },
    "name": "fast_browser_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read operation by 'Return' but does not disclose whether there are side effects, auth requirements, or rate limits. The mention of 'files and recent timeline' adds some context but is insufficient.

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?

One efficient sentence with no wasted words, appropriate for a simple tool. Could be slightly improved with structuring, but it is concise without being under-specified.

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 no output schema and no annotations, the description is too brief. It does not explain what 'QA state' contains, error conditions, or how the sessionId relates to the return value, leaving the agent with incomplete information.

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

Parameters1/5

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

Schema has 1 parameter (sessionId) with 0% description coverage, yet the description provides no additional meaning about the parameter, such as its format or purpose beyond what the schema minimally states.

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 the tool returns compact session QA state from files and recent timeline, with a specific verb and resource that distinguishes it from siblings like fast_browser_act or fast_browser_snapshot.

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?

No guidance on when to use this tool versus alternatives. With siblings for actions, diffs, errors, etc., the description should indicate the appropriate context for invoking this state-retrieval tool.

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