Skip to main content
Glama
Sign In
c2pa-mcp

c2pa-mcp

by harelrech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Scan a directory for C2PA content credentials

scan_c2pa_directory

Scan a directory of media files to identify those with C2PA Content Credentials, verify their trustworthiness, and determine AI generation status. Helps triage and assess provenance at scale.

Instructions

Audit a folder of media files: report which ones carry C2PA Content Credentials, their verdict, signer, and whether each is AI-generated. Non-recursive. Use this to triage a directory of images/videos at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "directory": "<directory>"
    },
    "name": "scan_c2pa_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxFilesNoMaximum number of media files to scan (default 200, max 1000).
directoryYesPath (or file:// URI) to the directory to scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses non-recursiveness and the output fields (C2PA presence, verdict, signer, AI-generation). It implies a read-only audit, but does not explicitly state no modifications or permissions needed. Slightly under-disclosed, but still useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. First sentence defines output scope, second sentence adds usage context and a key behavioral constraint. Highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description specifies the outputs (C2PA credentials, verdict, signer, AI-generated) without an output schema, which is adequate. Parameter count is low and well-documented in schema. Sibling tools provide context. Could mention whether it only scans media files or include a brief example, but overall complete.

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

Parameters3/5

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

Schema coverage is 100% with clear descriptions for both parameters (maxFiles with default and max, directory as path or URI). The tool description adds no further parameter-level details beyond the 'non-recursive' behavioral note, which is already stated. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool audits a folder of media files and reports C2PA credentials, verdict, signer, and AI-generation status. It specifies non-recursive behavior, distinguishing it from sibling tools that operate on single files or URLs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description includes an explicit usage directive ('Use this to triage a directory of images/videos at once'), providing clear context. It lacks explicit when-not-to-use guidance or alternatives, but sibling names imply differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools