Skip to main content
Glama
Sign In
FireKey MCP Server

FireKey MCP Server

by partnerhbhl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_stop

Stop a running FireKey browser profile by providing its profile ID or serial number to end the session and free up resources.

Instructions

Stop a running browser profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idNoProfile public ID
profile_noNoProfile serial number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.4/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 the full burden of behavioral disclosure. It merely restates the action implied by the name and gives no information about side effects, idempotency, error conditions, or what happens to the profile's state after stopping.

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 a single, front-loaded sentence with no wasted words. It states the action and the target resource directly, which is appropriately concise for a simple stop operation.

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?

With no annotations, no output schema, and all parameters optional in the schema, the description is too thin. It does not clarify that a profile identifier is likely required, what happens if the profile is not running, or what response is expected. An agent could attempt to call the tool with no arguments.

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%, and both parameters have clear descriptions ('Profile public ID' and 'Profile serial number'). However, the tool description adds no extra meaning about how these parameters should be used, such as whether one is preferred or whether both are acceptable.

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 uses a specific verb and resource: 'Stop a running browser profile.' It clearly distinguishes the tool from siblings like browser_start and browser_active, leaving no ambiguity about its core purpose.

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

Usage Guidelines3/5

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

The phrase 'Stop a running browser profile' implies the tool should be used when a browser profile is active, but it provides no explicit guidance on prerequisites, when not to use it, or alternatives. The usage context is clear only by inference from the action word 'stop.'

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