AOTrust - PDR Notarization

notary_free

Create a free cryptographic proof of existence (PDR) for a digital artifact without payment. Dual mode: pass work_hash (Mode A, client-computed SHA-256 hex) OR content (Mode B, raw text/code ≤60KB — server hashes it, zero retention). Subject to rate limits (5/IP/day, 1000/day global). Returns shield_id, pdr_b64, and verify_url. For on-chain settlement proof, use notary_notarize_paid ($0.01 USDC on Base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content`	No
`metadata`	No
`work_hash`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed8 schema fields changedSep 6, 2026

removedInput schema / properties / agent_pubkey

Removed value: -{
-  "default": "",
-  "type": "string"
-}

removedInput schema / properties / agent_sig

Removed value: -{
-  "default": "",
-  "type": "string"
-}

addedInput schema / properties / content

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / metadata

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / work_hash / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / work_hash / default
```
Added value: +null
```
removedInput schema / properties / work_hash / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "work_hash"
-]
```

AddedAug 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses free operation, rate limits (5/IP/day, 1000/day global), zero content retention, server-side hashing, and the returned identifiers. The one notable gap is the ambiguous 'OR' between work_hash and content — it does not state what happens if both are provided, nor does it mention metadata behavior.

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?

Four focused sentences, each earning its place: purpose, modes, limits, returns, and alternative route. Front-loaded with the core purpose and free nature, with supporting constraints and final routing. No wasted words.

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?

For a tool with an output schema, the description need not enumerate return values, but it does anyway — nice. It covers the main operational limits, retention behavior, and alternative. The gaps are the missing metadata parameter description and the unclear behavior when both content and work_hash are passed. Overall quite complete for a small free tool.

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 0%, so the description must compensate. It adds useful semantics for work_hash ('client-computed SHA-256 hex') and content ('raw text/code ≤60KB — server hashes it, zero retention'), but it completely omits the metadata parameter. The OR relationship between work_hash and content is also underspecified around mutual exclusivity.

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 opens with a specific action and resource: 'Create a free cryptographic proof of existence (PDR) for a digital artifact without payment.' It clearly distinguishes itself from the paid on-chain sibling by naming notary_notarize_paid and contrasting the free nature. The dual-mode explanation further clarifies what the tool does.

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?

Explicitly states when to use this tool (free proof, no payment) and when not to: 'For on-chain settlement proof, use notary_notarize_paid.' It also provides mode selection guidance for work_hash vs content. This is strong routing guidance that helps the agent choose correctly among siblings.

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

All AOTrust - PDR Notarization tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool serves a distinct purpose: free notarization, paid NEAR notarization, quote generation, verification, and a USDC discovery tool that is explicitly marked as non-callable. There is no ambiguity between the tools.

Naming Consistency5/5

All tools follow a consistent 'notary_' prefix with descriptive lowercase verbs (free, notarize, notarize_paid, quote, verify). The pattern is uniform and predictable.

Tool Count5/5

With 5 tools, the server is well-scoped for a notarization service. It covers the essential steps (free, quote, paid notarize, verify) without unnecessary bloat.

Completeness4/5

The toolset covers the core workflow: free PDR creation, paid NEAR notarization, and verification. However, the USDC-paid notarization tool is marked as discovery-only and cannot be used via MCP, leaving a minor gap in the paid options.

Resources

Need Help?