Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Verify C2PA provenance markers

evidence-intelligence_c2pa-provenance-verify

Look for local C2PA/JUMBF markers in uploaded bytes. Marker presence is not a factual authenticity determination. Price $0.05 USDC. POST /api/v1/evidence-intelligence/c2pa-provenance-verify. 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_c2pa-provenance-verify"
  }
}

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, the description must carry the behavioral burden. It usefully discloses the $0.05 USDC price, that unpaid calls return 402 and do not run, and that marker presence is not an authenticity determination. However, it does not describe the return format or output shape, and there is no output schema, leaving a significant behavioral gap.

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 four short sentences, front-loads the purpose, then adds the caveat, price, endpoint, and payment behavior. It is efficient and well ordered, with no wasted wording.

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, nested file inputs, no annotations, and no output schema, the description is incomplete. It covers commercial and caveat details but omits parameter guidance and return-value expectations, which an agent needs to invoke it 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% and there are seven parameters (csv, asOf, json, text, files, custodyEvents, expectedHashes). The description only says 'uploaded bytes' and does not explain what any parameter means, how files should be supplied, or which fields are relevant to verification. It barely compensates 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?

The description gives a specific verb and resource ('Look for local C2PA/JUMBF markers in uploaded bytes') and adds an important scope caveat that the result is not an authenticity determination. It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as integrity-recheck or metadata-extract.

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 guidance on when to use this tool versus alternatives like chain-of-custody-build or metadata-extract, nor any prerequisites or exclusions. Only commercial terms (price and 402 behavior) are provided, leaving the agent to infer usage context.

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