Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

firefox_parse_session_storage_tool

Parse Firefox session storage records from the sessionstore file in a given profile directory. Extract session storage data by host, key, and limit for forensic analysis.

Instructions

Parse Firefox session storage records when sessionstore contains them. Typical profile path: "C:\Users<user>\AppData\Roaming\Mozilla\Firefox\Profiles<rand>.default-release".

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": {
      "profile_path": "<profile_path>"
    },
    "name": "firefox_parse_session_storage_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional exact session storage key filter
hostNoOptional exact session storage host/origin filter
limitNoMaximum number of session storage records to return
profile_pathYesAbsolute path to the Firefox profile directory

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the burden. The phrase 'when sessionstore contains them' offers a condition, but there is no disclosure of side effects, return value, or safety profile. The word 'Parse' implies read-only, but this is not explicit.

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?

The description is two sentences and front-loaded with the main action. The profile path example is somewhat useful but not essential; still, it is concise and waste-free.

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

Completeness3/5

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

The output schema and parameter descriptions cover return values and inputs. The description adds the typical profile path and a condition about sessionstore, but it lacks explanation of how session storage differs from local storage or sessions, leaving some contextual gaps.

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%, so all parameters are documented in the schema. The tool description adds no extra parameter semantics, so the baseline of 3 applies.

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 parses Firefox session storage records, using a specific verb and resource. It distinguishes from siblings like firefox_parse_sessions_tool by the term 'session storage', though it does not explicitly name alternatives.

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 is provided on when to use this tool versus alternatives. It only mentions a typical profile path, which is a minor contextual hint but not usage guidance or exclusions.

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