Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Build forensic evidence report

evidence-intelligence_forensic-report

Aggregate hash, metadata, C2PA, custody, timeline, keyframe, location, duplicate, and integrity results. Distinguishes cryptographic integrity from factual authenticity. Price $0.08 USDC. POST /api/v1/evidence-intelligence/forensic-report. 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_forensic-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose valuable non-schema behavior: a price of $0.08 USDC, the POST endpoint, and that unpaid calls return 402 and do not execute — plus the important interpretive caveat that cryptographic integrity is distinct from factual authenticity. It does not say whether the report is persisted, whether it is read-only, or what happens with unexpected inputs, leaving meaningful gaps.

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?

Four short sentences, front-loaded with what is aggregated, then the key semantic caveat, then the commercial and transport facts. The closing payment/402 sentence is functionally necessary rather than padding. The long enumeration is dense but each item corresponds to a real analysis domain.

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 7-parameter, no-annotation, no-output-schema tool, the description leaves the agent guessing about input shapes and the report's structure and return format. It covers the commercial contract well (price, 402 no-op) and states one crucial interpretive nuance, but an agent still cannot tell what a successful response contains or how the csv/json/text/files inputs combine.

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?

Seven parameters exist with 0% schema description coverage, so the description must compensate and largely does not. The enumerated result domains loosely gesture at expectedHashes, custodyEvents, files, and text/json/csv payloads, but csv, asOf, text, and json receive no explanation at all, and the files array's role/label/parentId/expectedSha256 semantics are opaque without documentation.

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 verb 'Aggregate' plus the resource 'forensic evidence report' (implicit in the enumerations and title) clearly identifies this as the roll-up tool for the individual evidence analyzers. The listed domains (hash, metadata, C2PA, custody, timeline, keyframe, location, duplicate, integrity) map closely to the sibling tool names, so an agent can infer this composes them. It stops short of explicitly saying 'use this after running the individual extractors', so a 4 rather than 5.

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?

Usage is only implied: an agent infers this is the terminal step that combines prior analysis outputs into one report. There is no explicit when-to-use/when-not statement, no prerequisite ordering, and no named alternative for a single-domain-only query. The payment note is operational, not selection 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