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

browser-firefox-mcp

by ironessi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_session_info

Retrieve a complete session snapshot including cookies, storage, and detected authentication tokens to assess browser session state for security testing.

Instructions

Full session snapshot: cookies + storage + detected tokens.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior itself. The word 'snapshot' suggests a read-only operation, but it does not explicitly confirm non-destructiveness, mention authentication requirements, rate limits, or side effects. Some transparency via 'detected tokens' hinting at security checks, but it's not fully explicit.

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?

A single, well-structured sentence that front-loads the key purpose ('Full session snapshot') and lists contents. No wasted words or redundant information.

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?

Even without an output schema, the description conveys the main components returned. It could benefit from clarifying the structure of 'detected tokens' or stating that it's a holistic view, but it's adequate for a straightforward snapshot tool.

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

Parameters4/5

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

There are zero parameters, so the schema provides no info. The description adds value by detailing what the snapshot includes (cookies, storage, tokens), which helps the agent understand the output. Baseline for zero params is 4, and the description earns that.

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 ('snapshot') and clearly lists what it returns (cookies, storage, detected tokens). It distinguishes itself from sibling tools like get_cookies and get_storage_data by offering a combined, comprehensive view.

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 description implies it's for getting a full session overview, but does not explicitly state when to prefer it over targeted tools like get_cookies or get_storage_data, nor does it mention any exclusions or prerequisites.

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