Skip to main content
Glama

binary-forensics

sqlite_header_inspect

Inspect a SQLite3 database binary header (page size, schema cookie, encoding, WAL/journal version) and scan root B-tree SQL CREATE statements.

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

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short; it doesn't state that the operation is read-only, whether the file is modified, what happens on a non-SQLite or corrupt file, or any size/time constraints. It does disclose what data is extracted, which is some useful context, but the mutation and failure profile is entirely unstated.

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 front-loaded sentence that names the artifact first and then the extracted fields; the parenthetical list is dense but every element is informative, with no filler.

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

Completeness2/5

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

For a tool with two mutually-exclusive-looking input modes, no annotations, and no output schema, the description should clarify input selection and failure behavior. It covers the what-inspected well but leaves the agent guessing how to supply input and what an unsuccessful call looks like.

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

Parameters2/5

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

Schema description coverage is 0% and neither parameter is mentioned in the description. Critically, filePath and base64Data are both optional (required=0), so an agent gets no hint that these are alternative input modes or which to prefer — the description only weakly implies a file is the input.

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 pairs a specific verb ("Inspect") with a precise resource ("SQLite3 database binary header") and enumerates the fields examined (page size, schema cookie, encoding, WAL/journal version), plus a second capability (root B-tree CREATE statements). The explicit "SQLite3" qualifier distinguishes it from generic siblings like hexdump_inspect and binary_triage without needing to name them.

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 when-to-use guidance is given: it never states that this applies only to SQLite database files, nor when an agent should pick it over hexdump_inspect or binary_triage. The only implied context is the tool's subject matter, which an agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources