Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Extract evidence metadata

evidence-intelligence_metadata-extract

Extract container metadata from uploaded files locally. Missing EXIF or GPS fields are not invented. Price $0.04 USDC. POST /api/v1/evidence-intelligence/metadata-extract. 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_metadata-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose real behavior: local processing, a $0.04 USDC price, a 402 response for unpaid calls that do not execute, and a no-fabrication guarantee for missing EXIF/GPS. It says nothing about the response shape, size/time limits on 12MB base64 files, or whether anything is persisted, which matters for a forensic tool handling evidence payloads.

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 and zero filler; pricing, endpoint, and the payment gate are stated compactly. Structure is terse to the point of being telegraphic, but nothing is wasted.

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 tool with seven parameters, deeply nested base64 file inputs, no annotations, and no output schema, the description should explain at least the input model and what comes back. It covers purpose, cost, and honesty guarantees but leaves the entire parameter surface and the return behavior undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven parameters, including nested objects like files (with mediaType enum, expectedSha256, capturedAt), custodyEvents, and expectedHashes. The description adds no meaning for any of them—no explanation of asOf, csv/json/text inputs, or how expectedHashes relates to expectedSha256.

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?

"Extract container metadata from uploaded files locally" gives a specific verb (extract) plus a scoped resource (container metadata from uploaded files) and a processing locality constraint. It is clear enough to separate from siblings like file-hash-manifest or c2pa-provenance-verify, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no reference to the sibling tools it competes with (hash manifest, C2PA verify, chain-of-custody). The only operational conditions stated are payment related (unpaid calls return 402), 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