Skip to main content
Glama
Sign In
floppydata-mcp

floppydata-mcp

Official
by Floppydata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stop_browser_session

Stops a Cloud Browser session and saves its persistent state, letting agents end browser automation and later resume from the saved state.

Instructions

Stop a Cloud Browser session and save its persistent browser state. Safe to call more than once.

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": "stop_browser_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesBrowser session id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.4/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 usefully discloses two behavioral traits: the session persists browser state, and the call is idempotent ("Safe to call more than once"). It does not say whether stopping is blocking, whether the saved state can later be resumed, or what happens to in-flight work.

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 short sentences with zero waste, front-loading the action and then the side effect, with the idempotency note last. Nothing needs trimming or reordering.

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?

For a simple one-parameter tool with no output schema and no annotations, the description covers the action, the side effect, and retry safety. It stops short of clarifying the semantics of "persistent browser state" or how this differs from delete_browser_session, which is the one gap an agent would hit.

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% for the single required sessionId parameter, so the schema already documents it. The description adds no format, sourcing, or lookup details beyond what is structured, making 3 the correct baseline.

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?

Specific verb and resource ("Stop a Cloud Browser session") plus the side effect of saving persistent browser state. This implicitly separates it from the sibling delete_browser_session, but the distinction is never made explicit, so an agent must infer it.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the closely related delete_browser_session as an alternative. The only hint is that stopping preserves state, from which the agent must infer that deleting would not.

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