PrivateDAO Agent Exchange

PrivateDAO Workflow Guide

get_workflow_guide

Read-onlyIdempotent

Return the overview, execution, or payment workflow guide. Use this instead of separate guide tools when you need lifecycle context; it is free, read-only, and returns the selected next steps without executing or paying.

Input Schema

Name	Required	Description	Default
`topic`	Yes	Choose the lifecycle guide needed before discovery, execution, or payment.

Output Schema

Name	Required	Description
`free`	No	Free-service path when the payment topic is selected.
`name`	No	Exchange or workflow name.
`paid`	No	Ordered paid-service steps when the payment topic is selected.
`rules`	No	Safety rules for the selected workflow.
`states`	No	Possible request states.
`payment`	No	Payment rules for the selected workflow.
`endpoints`	No	Machine endpoints for the selected workflow.
`lifecycle`	No	Ordered lifecycle stages.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured workflow guidance selected by topic.",
+  "properties": {
+    "endpoints": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Machine endpoints for the selected workflow.",
+      "type": "object"
+    },
+    "free": {
+      "description": "Free-service path when the payment topic is selected.",
+      "type": "string"
+    },
+    "lifecycle": {
+      "description": "Ordered lifecycle stages.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Exchange or workflow name.",
+      "type": "string"
+    },
+    "paid": {
+      "description": "Ordered paid-service steps when the payment topic is selected.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": true,
+      "description": "Payment rules for the selected workflow.",
+      "type": "object"
+    },
+    "rules": {
+      "description": "Safety rules for the selected workflow.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "states": {
+      "description": "Possible request states.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedOct 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds genuinely new traits: the call is free, returns next steps, and has no side effects on execution or payment. This is real value beyond the structured hints, though it does not say anything about ordering or whether guides reference later steps.

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 with the purpose front-loaded and the routing/constraint info second. "it is free, read-only" slightly duplicates the annotations, but the waste is minimal.

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 single-enum, read-only lookup tool with an output schema and full annotation coverage, the description covers purpose, cost, and safety adequately. The only residual gap is that it references non-existent "separate guide tools," which could confuse an agent scanning the sibling list.

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% and the enum values are already documented with per-value guidance ("before discovery, execution, or payment"). The description only restates the three topic names, adding no format or selection nuance beyond the schema — baseline 3.

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 ("Return") and resource ("overview, execution, or payment workflow guide"), and enumerates the three topic variants so the agent knows the scope without opening the schema. The sibling differentiation is weakened because it says to use it "instead of separate guide tools," but no such tools exist in the sibling list, leaving the agent to guess what it replaces.

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?

"Use this instead of separate guide tools when you need lifecycle context" gives an explicit trigger and a named alternative, and the trailing clause clarifies a when-not (it does not execute or pay). The guidance is clear but slightly abstract — "lifecycle context" is not tied to concrete agent goals like 'before calling create_paid_job'.

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.