Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Cluster duplicate evidence

evidence-intelligence_duplicate-cluster

Cluster uploaded evidence files that share the same sha256 digest. Duplicates are cryptographic only. Price $0.03 USDC. POST /api/v1/evidence-intelligence/duplicate-cluster. 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_duplicate-cluster"
  }
}

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?

With no annotations supplied, the description does carry real behavioral context: pricing ($0.03 USDC), the payment gate (402 returns without execution), and the HTTP endpoint. What it omits is whether evidence is persisted or merely analyzed, and whether the call has write side effects — important for a tool whose schema takes base64 file uploads.

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 with the purpose front-loaded, then cost and endpoint facts. Every sentence adds an operational fact; the raw endpoint path is the least valuable line but still relevant for API callers.

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?

The schema is complex (nested files, custodyEvents, expectedHashes arrays, 7 top-level params, none required) with no output schema and no annotations. The description explains none of the input modes or the return shape, leaving an agent unable to know what to send or what comes back beyond 'clusters'.

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. Only the sha256 notion loosely maps to expectedSha256/expectedHashes, while csv, text, json, asOf, files, and custodyEvents are never explained anywhere.

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 ('Cluster uploaded evidence files') plus the exact matching criterion ('same sha256 digest'), which is more than a restatement of the name. It does not explicitly contrast itself with hash-manifest or integrity-recheck siblings, so it falls short of a 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?

'Duplicates are cryptographic only' usefully narrows the meaning of 'duplicate' to digest equality rather than perceptual similarity. However, there is no explicit when-to-use/when-not guidance and no routing to an alternative sibling when the agent wants hashing without clustering.

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