PrivateDAO Agent Exchange

PrivateDAO PrivatePay Architecture

privatepay_status

Read-onlyIdempotent

Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Call this first; it is free and read-only, creates no challenge, and never moves funds.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`enabled`	No	Whether the private settlement rail is currently enabled for new payment operations.
`network`	No	Settlement network identifier.
`privacy`	No	Provider-visible and public-chain privacy boundaries.
`pdao_required`	No	Whether the private path requires the PDAO entry policy.
`settlement_mode`	No	Configured provider settlement mode.
`activation_blockers`	No	Explicit blockers when the rail is unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

changedInput schema / description

Previous value: -"Return the fail-closed readiness and privacy boundaries for PrivatePAY x402."New value: +"Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Use this first; it never creates a challenge or payment."

addedOutput schema / properties

Added value: +{
+  "activation_blockers": {
+    "description": "Explicit blockers when the rail is unavailable.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "enabled": {
+    "description": "Whether the private settlement rail is currently enabled for new payment operations.",
+    "type": "boolean"
+  },
+  "network": {
+    "description": "Settlement network identifier.",
+    "type": "string"
+  },
+  "pdao_required": {
+    "description": "Whether the private path requires the PDAO entry policy.",
+    "type": "boolean"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Provider-visible and public-chain privacy boundaries.",
+    "type": "object"
+  },
+  "settlement_mode": {
+    "description": "Configured provider settlement mode.",
+    "type": "string"
+  }
+}

Changed2 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Use this first; it never creates a challenge or payment."New value: +"Return the fail-closed readiness and privacy boundaries for PrivatePAY x402."

removedOutput schema / properties

Removed value: -{
-  "activation_blockers": {
-    "description": "Explicit blockers when the rail is unavailable.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "enabled": {
-    "description": "Whether the private settlement rail is currently enabled for new payment operations.",
-    "type": "boolean"
-  },
-  "network": {
-    "description": "Settlement network identifier.",
-    "type": "string"
-  },
-  "pdao_required": {
-    "description": "Whether the private path requires the PDAO entry policy.",
-    "type": "boolean"
-  },
-  "privacy": {
-    "additionalProperties": true,
-    "description": "Provider-visible and public-chain privacy boundaries.",
-    "type": "object"
-  },
-  "settlement_mode": {
-    "description": "Configured provider settlement mode.",
-    "type": "string"
-  }
-}

Changed2 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Return the fail-closed readiness and privacy boundaries for PrivatePAY x402."New value: +"Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Use this first; it never creates a challenge or payment."

addedOutput schema / properties

Added value: +{
+  "activation_blockers": {
+    "description": "Explicit blockers when the rail is unavailable.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "enabled": {
+    "description": "Whether the private settlement rail is currently enabled for new payment operations.",
+    "type": "boolean"
+  },
+  "network": {
+    "description": "Settlement network identifier.",
+    "type": "string"
+  },
+  "pdao_required": {
+    "description": "Whether the private path requires the PDAO entry policy.",
+    "type": "boolean"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Provider-visible and public-chain privacy boundaries.",
+    "type": "object"
+  },
+  "settlement_mode": {
+    "description": "Configured provider settlement mode.",
+    "type": "string"
+  }
+}

Changed2 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Use this first; it never creates a challenge or payment."New value: +"Return the fail-closed readiness and privacy boundaries for PrivatePAY x402."

removedOutput schema / properties

Removed value: -{
-  "activation_blockers": {
-    "description": "Explicit blockers when the rail is unavailable.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "enabled": {
-    "description": "Whether the private settlement rail is currently enabled for new payment operations.",
-    "type": "boolean"
-  },
-  "network": {
-    "description": "Settlement network identifier.",
-    "type": "string"
-  },
-  "pdao_required": {
-    "description": "Whether the private path requires the PDAO entry policy.",
-    "type": "boolean"
-  },
-  "privacy": {
-    "additionalProperties": true,
-    "description": "Provider-visible and public-chain privacy boundaries.",
-    "type": "object"
-  },
-  "settlement_mode": {
-    "description": "Configured provider settlement mode.",
-    "type": "string"
-  }
-}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties

Added value: +{
+  "activation_blockers": {
+    "description": "Explicit blockers when the rail is unavailable.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "enabled": {
+    "description": "Whether the private settlement rail is currently enabled for new payment operations.",
+    "type": "boolean"
+  },
+  "network": {
+    "description": "Settlement network identifier.",
+    "type": "string"
+  },
+  "pdao_required": {
+    "description": "Whether the private path requires the PDAO entry policy.",
+    "type": "boolean"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Provider-visible and public-chain privacy boundaries.",
+    "type": "object"
+  },
+  "settlement_mode": {
+    "description": "Configured provider settlement mode.",
+    "type": "string"
+  }
+}

Changed1 schema field changedOct 25, 2026

changedInput schema / description

Previous value: -"Return the fail-closed readiness and privacy boundaries for PrivatePAY x402."New value: +"Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Use this first; it never creates a challenge or payment."

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Fail-closed PrivatePAY readiness and privacy status.",
+  "type": "object"
+}

AddedOct 20, 2026

TDQS

A4.5/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. The description adds value beyond them by asserting the call is free (a cost trait annotations cannot express) and that it creates no challenge and never moves funds, which is the domain-specific risk an agent needs to know before sequencing payment tools.

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?

One sentence to enumerate the reported state, one short clause to establish the call-first ordering and safety profile. Front-loaded, no filler, every clause carries information.

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?

With no parameters and an output schema present, the description only needs to convey purpose, sequencing, and safety, all of which it covers. Nothing required to invoke this correctly is missing.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline 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 ("Read") and enumerates the exact resources returned: x402 readiness, MagicBlock rail config, facilitator state, PDAO entry requirement, and public-chain privacy boundary. This is clearly distinguishable from the sibling privatepay_challenge/prepare/settle/verify tools, which act rather than report.

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?

"Call this first" gives explicit ordering guidance relative to the other privatepay_* siblings, and the free/read-only framing tells the agent this is the safe entry point. It stops short of naming which sibling to move to next or stating exclusions, so it is clear context rather than a full decision rule.

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

All PrivateDAO Agent Exchange 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.

PrivateDAO PrivatePay Architecture

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources