Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

firefox_profile_summary_tool

Summarize Firefox profile artifacts for forensic analysis, detecting presence of history, bookmarks, downloads, cookies, sessions, favicons, extensions, preferences, and login metadata.

Instructions

Summarize basic Firefox artifacts available in a browser profile. Typical Firefox profile path: "C:\Users<user>\AppData\Roaming\Mozilla\Firefox\Profiles<rand>.default-release". Extract with disk-forensics first, then point this tool at the extracted directory.

Detects whether history, bookmarks, downloads, cookies, sessions, favicons, extensions, preferences, and login metadata artifacts are present.

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_profile_summary_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_pathYesAbsolute path to the Firefox profile directory
sample_limitNoMaximum number of sample identifiers per artifact

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It accurately states that the tool only 'Detects whether' artifacts are present, setting expectations that it is a summary/presence check rather than a deep parser. It also gives a typical profile path, aiding correct usage. However, it doesn't explicitly state the tool is read-only or non-destructive, though that is implied.

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 compact (four sentences) and front-loaded with the main purpose. Every sentence adds value: the purpose, a typical path, a usage prerequisite, and the list of detected artifacts. No redundant or filler content.

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?

The tool has an output schema (per context signals), so the description needn't explain return values. It covers the essential context: what the tool does, what artifacts it checks for, the expected profile path, and a prerequisite step. It could slightly improve by explicitly noting that this is a triage step before using specific parse tools, but current completeness is high.

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%, with both parameters already well-documented in the schema. The description adds only a typical path example but no new semantics beyond the schema's 'Absolute path' and 'Maximum number of sample identifiers per artifact.' Baseline 3 applies when the schema handles parameter explanation.

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 the tool's action ('Summarize basic Firefox artifacts available in a browser profile') and identifies the specific resource (the Firefox profile). It also lists concrete artifact types it detects, distinguishing it from sibling parse tools that target individual artifacts.

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

Usage Guidelines4/5

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

The description gives explicit workflow guidance: 'Extract with disk-forensics first, then point this tool at the extracted directory.' It implies this tool is for triage/summary before using more specific parse tools, though it does not explicitly name those alternatives or state 'use this before firefox_parse_*'.

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