Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Recheck evidence integrity

evidence-intelligence_integrity-recheck

Compare current local hashes to caller-supplied expected digests. A match verifies cryptographic integrity only. Price $0.03 USDC. POST /api/v1/evidence-intelligence/integrity-recheck. 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_integrity-recheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 disclose genuinely operational facts the schema cannot: price ($0.03 USDC), transport (POST /api/v1/evidence-intelligence/integrity-recheck), and the failure mode that unpaid calls return 402 and do not run. It also scopes what a match proves. The gap is that it never says what a mismatch returns or how results are reported.

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 front-loaded sentences, with the core behavior first and cost/transport/payment failure following. Nearly every sentence earns its place; the raw endpoint path is modestly redundant with the tool name but still useful operationally.

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, 0%-coverage, deeply nested tool with no annotations and no output schema, the description is thin. It leaves the return format entirely unexplained and does not account for the non-hash inputs, so an agent cannot confidently decide which fields to populate or what a response will contain.

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, several of them nested arrays (files[] with fileBase64/expectedSha256, expectedHashes[] with an algorithm enum, custodyEvents[]). The description only gestures at 'expected digests', which maps loosely to expectedHashes/files[].expectedSha256, and says nothing about csv, json, text, asOf, or why custodyEvents belongs in an integrity recheck. It does not compensate for the coverage gap.

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+resource: 'Compare current local hashes to caller-supplied expected digests.' That is materially clearer than the name alone, and 'A match verifies cryptographic integrity only' bounds the claim. It does not, however, distinguish this from the sibling file-hash-manifest or explain which input fields carry the digests being compared.

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?

No explicit when-to-use or when-not-to-use guidance versus alternatives, and no named sibling. Implied usage is derivable from 'compare current local hashes to caller-supplied expected digests', and the caveat that a match proves cryptographic integrity only implicitly tells the caller not to treat it as provenance or authenticity verification.

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