Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

chromium_parse_history_tool

Extract Chromium browsing history from a given profile path, with optional URL, title, and record limit filters to locate specific forensic evidence.

Instructions

Parse Chromium browsing history records from a browser profile. Typical profile path: "C:\Users<user>\AppData\Local\Google\Chrome\User Data\Default".

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional exact URL filter
limitNoMaximum number of history records to return
titleNoOptional exact page title filter
profile_pathYesAbsolute path to the Chromium profile directory

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only says 'Parse' without addressing whether the tool is read-only, requires the browser to be closed, or handles locked or encrypted profiles. The typical path example adds some context, but significant behavioral gaps remain (e.g., side effects, prerequisites).

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 extremely concise, consisting of two short sentences. It front-loads the core action and resource, includes a useful path example, and contains no filler or redundancy.

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 tool has an output schema, so return values are presumably covered elsewhere. However, the description lacks context on important prerequisites (e.g., profile must not be in use, chrome version compatibility) and any limitations (e.g., whether it only reads SQLite files or handles encrypted history). It is adequate but not rich enough for a complex parsing tool.

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 coverage is 100%, so the parameters (url, limit, title, profile_path) are fully described in the schema. The description adds no additional parameter semantics beyond repeating the profile path example, which is already in the schema. Baseline of 3 is appropriate.

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 parses Chromium browsing history records from a browser profile, using a specific verb ('Parse') and resource ('history records'). This distinguishes it from sibling tools that parse other data types (bookmarks, cookies, etc.) or from Firefox history parsing.

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 provides clear context by specifying 'Chromium' and giving a typical profile path, which implies the tool is for use with Chromium-based browsers and for history records specifically. However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of full 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