Skip to main content
Glama
Sign In

Privi

by com.onrender.privi-ledger
OverviewDiscussionsAdmin

Content Seal: seal files or text

seal_content

Seal content your company publishes (documents, images, video, press releases, invoices, AI output) with who made it and whether AI was involved. Each seal is anchored on chain; anyone can check a file for free at the returned verify_url or with seal_verify. Counts toward your plan's monthly entries. Requires the organization API key.

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": {
      "items": "<items>"
    },
    "name": "seal_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes1-50 items: {sha256: '<64-hex of the file>' (or text: 'exact text'), origin: human|ai_assisted|ai_edited|ai_generated, ai_tool (required unless human), title, author, media_type, note}. Only the fingerprint is sent, never the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the mutation/read-only profile, and the description adds value on top: on-chain anchoring, free public verification, consumption of the plan's monthly entry quota, and the organization API key requirement. Doesn't say what happens when the same fingerprint is sealed twice, though idempotentHint=false already signals duplication is possible.

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?

Three sentences, front-loaded with the action and the payload, with auth and quota constraints trailing. No filler or restatement of the title.

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?

With no output schema, the description usefully names the one return value that matters (verify_url). Auth, quota and verification paths are all present; only edge behavior on duplicate seals and the response for batch items is left implicit.

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% and the nested items description already enumerates sha256/text, origin, ai_tool, title, author, media_type and note. The prose adds only a high-level gloss ('who made it and whether AI was involved') and the privacy note that only the fingerprint is sent, so baseline 3 applies.

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?

States a specific verb ('seal') plus the resource scope (published documents, images, video, invoices, AI output) and what the seal records (originator and AI involvement). Clearly separable from seal_verify / seal_list / seal_revoke siblings.

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?

Gives a concrete context ('content your company publishes') and routes verification to seal_verify or the returned verify_url. Missing only explicit when-not-to-use guidance or a statement of what to do if a seal already exists.

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

All Privi toolsInspect
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