Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Build evidence file hash manifest

evidence-intelligence_file-hash-manifest

Hash uploaded evidence bytes locally with md5, sha1, sha256, and sha512. Hash matches verify cryptographic integrity only, not factual authenticity. Price $0.04 USDC. POST /api/v1/evidence-intelligence/file-hash-manifest. Unpaid calls return 402 and do not run.

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": "evidence-intelligence_file-hash-manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a solid job: it discloses that hashing happens locally, that results prove cryptographic integrity only, that the call costs $0.04 USDC, and that unpaid calls return 402 without executing. Missing are persistence/retention behavior for the uploaded bytes and any payload size or rate limits, which matter for a tool accepting large base64 files.

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 operation is front-loaded in the first sentence, and each subsequent sentence adds a distinct fact (semantic caveat, price, endpoint, 402 behavior). The endpoint path is somewhat boilerplate but still useful for constructing the call; no sentence is pure filler.

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

Completeness5/5

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

Placeholder.

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% across 7 parameters, so the description must compensate and largely does not — nothing explains files/fileBase64, expectedSha256, expectedHashes, custodyEvents, or the csv/json/text alternatives. The only overlap is the algorithm list (md5/sha1/sha256/sha512), which mirrors the expectedHashes enum without adding meaning.

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 names a specific verb and resource ('Hash uploaded evidence bytes locally') and enumerates the four algorithms produced, so the operation is unmistakable. It stops short of explicitly contrasting with the closest sibling (evidence-intelligence_integrity-recheck), so an agent must infer which one to pick.

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?

There is no guidance on when to choose this tool over integrity-recheck, chain-of-custody-build, or metadata-extract, and no stated preconditions. The only usage-adjacent statement is the caveat that hash matches verify integrity rather than factual authenticity, which is a scope limit rather than routing guidance.

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