Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Extract video keyframe evidence

evidence-intelligence_video-keyframe-extract

Inspect local video container metadata and hash caller-supplied keyframe image files. Frames are not decoded by external services. Price $0.05 USDC. POST /api/v1/evidence-intelligence/video-keyframe-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_video-keyframe-extract"
  }
}

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 provided, the description carries the full disclosure burden. It usefully states the price ($0.05 USDC), the HTTP endpoint, that unpaid calls return 402 and do not run, and that frames are not decoded by external services. However, it omits permissions, rate limits, storage/retention behavior, and what the tool returns.

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?

The description is short and front-loads the core operation before adding processing, pricing, and payment-failure details. Every sentence provides relevant information, though the raw endpoint path is less useful to an agent than additional parameter or usage detail would be.

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 7 top-level parameters, nested input structures, no annotations, and no output schema, the description is too thin. It covers payment behavior and one processing boundary, but it does not explain the parameters, expected inputs such as custody events or expected hashes, or what the agent should expect back.

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 but does not. It vaguely points to caller-supplied keyframe image files and hashing, which may relate to files and expectedHashes, but it gives no meaning for csv, json, text, asOf, or custodyEvents. Most parameter semantics are left to an undocumented schema.

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?

The description states a specific operation: inspect local video container metadata and hash caller-supplied keyframe image files. It also clarifies that frames are not decoded by external services, which distinguishes the operation from actual frame extraction. It does not explicitly differentiate itself from sibling tools such as metadata-extract or file-hash-manifest.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no named alternatives. The phrase 'caller-supplied keyframe image files' weakly implies the caller must already have keyframes, but this is not framed as usage guidance. It does not help an agent choose between this tool and related evidence-intelligence siblings.

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