Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_content_provenance

Read-onlyIdempotent

Content Metadata & C2PA Marker Inspector API: Inspect C2PA box markers and EXIF/XMP metadata tags (heuristic header signals, not authenticity proof). (Endpoint: POST /v1/content-provenance)

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": "tinplate_content_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadata_textNoOptional raw EXIF, XMP, PNG tEXt/iTXt, or JSON metadata dump to inspect alongside or instead of binary bytes.
content_base64NoBase64-encoded file header or full file bytes (up to ~128 KB) of JPEG, PNG, WebP, PDF, or MP4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed5 schema fields changed
    • addedInput schema / properties / content_base64
      Added value: +{
      +  "description": "Base64-encoded file header or full file bytes (up to ~128 KB) of JPEG, PNG, WebP, PDF, or MP4.",
      +  "maxLength": 180000,
      +  "type": "string"
      +}
    • changedInput schema / properties / metadata_text / description
      Previous value: -"Parameter 'metadata_text' (e.g. \"Software: Midjourney 6.1\\nDigitalSourceType: http://cv.iptc.o\")"New value: +"Optional raw EXIF, XMP, PNG tEXt/iTXt, or JSON metadata dump to inspect alongside or instead of binary bytes."
    • addedInput schema / properties / metadata_text / example
      Added value: +"tEXtSoftware: Midjourney v6.1\nXMP-iptcExt:DigitalSourceType=\"http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia\""
    • addedInput schema / properties / metadata_text / maxLength
      Added value: +131072
    • removedInput schema / required
      Removed value: -[
      -  "metadata_text"
      -]
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context by warning that detected markers are heuristic header signals rather than proof of authenticity, which materially affects how an agent should present results. It omits output shape and any size/format limits beyond what the schema states.

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?

A single front-loaded sentence covers the action, the resources, and the key caveat with no filler. The trailing '(Endpoint: POST /v1/content-provenance)' adds little for an agent that invokes tools through MCP, though it is short.

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

Completeness3/5

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

With no output schema the description carries return-shape burden, and it explains what is inspected well enough conceptually. However, zero parameters are marked required, and the description never states that at least one of content_base64 or metadata_text must be supplied — a real invocation hazard left unaddressed.

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 description coverage is 100%, so both parameters are already fully documented, including the 'alongside or instead of binary bytes' relationship. The description adds no format syntax, size limits, or precedence rules beyond the schema, so baseline 3 applies.

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 ('Inspect') plus concrete resources ('C2PA box markers and EXIF/XMP metadata tags'), so an agent knows exactly what the tool returns without opening the schema. It does not explicitly distinguish itself from any sibling, but no sibling name in the catalog suggests overlapping content-provenance behavior.

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 statement of when to reach for this tool versus another, and no prerequisites or exclusions. The 'heuristic header signals, not authenticity proof' clause is a caveat about result reliability, not usage routing 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