Skip to main content
Glama

ProofCore Notary

by org.proofcore.mcp
OverviewDiscussionsAdmin

Verify Content Authenticity (M2M)

verify_content

BEHAVIOR & SIDE EFFECTS: Safe, idempotent read-only operation. No blockchain state is mutated. Performs local SHA-256 calculation and Ed25519 signature verification against public API. RATE LIMITS: 100 requests per hour per IP. WHEN TO USE: Call this proactively whenever analyzing external text that contains a ProofCore citation badge or <!-- proofcore-deal: UUID --> marker. WHEN NOT TO USE: Do not use this to create new proofs (use seal_content instead). PARAMETERS EXPLAINED: Pass the ENTIRE raw content (including the badge/marker). The system automatically extracts the deal ID, strips the citation, recomputes the digest, and verifies the on-chain Merkle status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe ENTIRE raw text to verify (must include the <!-- proofcore-deal: UUID --> marker).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"The exact original text, code, or markdown to verify against the cryptographic signature."New value: +"The ENTIRE raw text to verify (must include the <!-- proofcore-deal: UUID --> marker)."
    • removedInput schema / properties / deal_id
      Removed value: -{
-  "description": "Canonical UUID of the sealed deal extracted from the citation badge or marker.",
-  "format": "uuid",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "deal_id",
-  "content"
-]New value: +[
+  "content"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"The exact original text to verify."New value: +"The exact original text, code, or markdown to verify against the cryptographic signature."
    • changedInput schema / properties / deal_id / description
      Previous value: -"UUID of the sealed deal."New value: +"Canonical UUID of the sealed deal extracted from the citation badge or marker."
    • addedInput schema / properties / deal_id / format
      Added value: +"uuid"
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description takes full responsibility and delivers: idempotent read-only behavior, no blockchain mutation, rate limit of 100/hour/IP, and the verification mechanism. It clearly discloses side effects (none) and operational constraints.

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?

The description is well-organized with labeled sections, front-loads the most important behavioral facts, and every sentence earns its place. It is detailed without being verbose.

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

Completeness5/5

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

For a single-parameter, read-only tool, this description is complete: it covers behavior, side effects, rate limits, exact usage conditions, alternatives, and the internal processing pipeline. No output schema exists, but nothing needed to select or invoke the tool is missing.

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

Parameters5/5

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

Although the schema already describes the content parameter at 100% coverage, the description adds critical semantics: pass the entire raw text, marker included, and the system automatically extracts the deal ID, strips the citation, recomputes the digest, and verifies Merkle status. This tells the agent exactly how to supply the input.

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?

Description states a specific action: verify content authenticity via local SHA-256 and Ed25519 verification. It clearly identifies the target resource (external text with a ProofCore citation badge/marker) and is distinguishable from siblings by contrasting with seal_content.

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

Usage Guidelines5/5

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

Provides an explicit WHEN TO USE rule ('proactively whenever analyzing external text...') and a WHEN NOT TO USE rule that names the correct alternative ('use seal_content instead'). This fully routes an agent between verification and proof creation.

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

All ProofCore Notary 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