Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Build image source timeline

evidence-intelligence_image-source-timeline-build

Combine caller-supplied capture times, local EXIF timestamps, and custody events into an image timeline. Price $0.04 USDC. POST /api/v1/evidence-intelligence/image-source-timeline-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_image-source-timeline-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
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does disclose two genuinely useful facts an agent cannot get from the schema: a $0.04 USDC price and that unpaid calls return 402 without executing. What it omits is the data-handling profile — whether uploaded files are retained, whether the built timeline is persisted or returned only, and whether the operation is repeatable/deterministic.

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, front-loaded with the action and inputs before billing and transport details. The raw endpoint path is arguably boilerplate, but each sentence carries distinct information and there is no filler.

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 tool with 0 required fields, zero schema coverage, no annotations, and no output schema, the description is thin. It never describes the shape of the returned timeline, the semantics of the four interchangeable content inputs, or the precedence rules that determine what the merged timeline looks like — all things an agent needs to call this 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 top-level parameters, so the description must compensate and largely does not. Naming 'capture times' and 'custody events' hints at the files and custodyEvents arrays, but csv, json, text, asOf, and expectedHashes are left entirely unexplained, including the precedence between the four alternative input channels and which timestamp source wins on conflict.

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 concrete verb and output: 'Combine caller-supplied capture times, local EXIF timestamps, and custody events into an image timeline.' The three input sources give an agent a concrete sense of what gets merged, which loosely separates it from siblings like chain-of-custody-build or metadata-extract. It stops short of naming an alternative explicitly, so a 4 rather than 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 Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to pick this over chain-of-custody-build or metadata-extract, and no prerequisites or preconditions are stated. The only routing information is the payment gate (402), which is about billing, not tool selection.

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