Tinplate Edge AI Safety, Security & EU Compliance

tinplate_content_provenance

Read-onlyIdempotent

Synthetic Content Provenance Checker API: Detect C2PA manifests, AI generator EXIF/XMP tags, and stripped metadata in files or headers. (Endpoint: POST /v1/content-provenance)

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": {
      "metadata_text": "<metadata_text>"
    },
    "name": "tinplate_content_provenance"
  }
}

Input Schema

Name	Required	Description	Default
`metadata_text`	Yes	Parameter 'metadata_text' (e.g. "Software: Midjourney 6.1\nDigitalSourceType: http://cv.iptc.o")

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the detection categories and the endpoint path, but says nothing about what a result looks like (match/no-match, confidence, manifest detail) or how stripped metadata is reported, and the 'files or headers' wording does not map cleanly onto a text-only input.

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?

Two compact sentences, front-loaded with the capability and ending with the endpoint, with no filler. The endpoint parenthetical is marginally useful but harmless.

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?

For a one-parameter read-only checker this covers what is detected and the transport endpoint. Since there is no output schema, the description should have described the shape of the result (e.g., whether C2PA/AI-tag/stripped flags are returned), which is the main remaining gap.

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% with a single required parameter, so the schema carries the burden and baseline 3 applies. The description adds no detail about what metadata_text should contain (raw EXIF block vs. header dump vs. JSON), and 'files or headers' may mislead an agent into thinking it can pass a file rather than a text blob.

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 specific verb (Detect) and concrete resources (C2PA manifests, AI generator EXIF/XMP tags, stripped metadata), which is far more informative than the name alone. It does not explicitly contrast itself with siblings, but the purpose is unambiguous enough to route correctly.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'in files or headers' – an agent can infer this is for provenance/synthetic-media verification. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling guard/scanner tools.

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

All Tinplate Edge AI Safety, Security & EU Compliance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?