Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Build evidence chain of custody

evidence-intelligence_chain-of-custody-build

Order supplied custody events per evidence id and compare optional hashAfter values to current sha256 digests. Price $0.04 USDC. POST /api/v1/evidence-intelligence/chain-of-custody-build. 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_chain-of-custody-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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. It usefully discloses pricing ($0.04 USDC) and the 402 unpaid-call behavior, but never says what happens when a hashAfter value mismatches the computed digest, whether the call fails or reports mismatches, or what the built chain looks like.

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?

Three short sentences with the core behavior front-loaded; nothing is padded. The raw POST path is largely redundant with the tool name and sibling namespace, but it is only a minor waste.

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?

This is a complex, 7-parameter tool with no output schema and no annotations, yet the description omits return shape, mismatch handling, and the roles of the input-mode and hash-list parameters. It covers payment gating but not the verification semantics an agent needs to call it correctly.

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. It gives some meaning for custodyEvents (order per evidenceId) and hashAfter, but leaves files, expectedHashes, asOf, csv, json, and text completely unexplained, including how the text/csv/json input modes differ from structured events.

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?

States a specific verb and resource: orders supplied custody events per evidence id and compares hashAfter values against computed sha256 digests. That is concrete enough for an agent to distinguish it from siblings such as file-hash-manifest or integrity-recheck, though it never names an alternative explicitly.

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 implicit in the described operation — an agent can infer it should call this when it already has custody events and wants an ordered chain plus hash verification. There is no explicit when-to-use, when-not-to-use, or named alternative tool.

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