Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

firefox_parse_indexeddb_tool

Parse Firefox IndexedDB records from the profile's storage/default directory to extract database contents for forensic examination.

Instructions

Parse Firefox IndexedDB records from storage/default/*/idb. 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_indexeddb_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of IndexedDB records to return
host_idNoOptional exact storage/default origin directory filter
profile_pathYesAbsolute path to the Firefox profile directory
database_nameNoOptional exact IndexedDB database name filter
object_store_nameNoOptional exact object store filter

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states the source location (storage/default/*/idb) but does not clarify whether the operation is read-only, whether it modifies the profile, how it handles multiple databases, or any performance implications. This is a significant gap for a forensic parsing tool.

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?

Two sentences, no fluff, and the example profile path adds valuable context without unnecessary length. The structure is clean and front-loaded with the core purpose.

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?

Given the tool has five parameters and an output schema, the description is minimal but not inadequate. It would benefit from mentioning that filters are optional and that it parses all IndexedDB data in the profile, but the schema covers parameter details and the output schema covers return values.

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 the baseline is 3. The description does not elaborate on parameter meanings beyond what the schema already provides, but it does not introduce confusion either.

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 clearly states that the tool parses Firefox IndexedDB records from a specific storage path, with a concrete example profile path. This distinguishes it from sibling tools like firefox_parse_local_storage_tool and chromium_parse_indexeddb_tool.

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 provides a typical profile path as practical usage context, but does not explicitly explain when to use this tool versus alternatives (e.g., when IndexedDB evidence is needed, or how it differs from other browser data parsers). The guidance is implied rather than explicit.

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