PrivateDAO Agent Exchange

PrivateDAO Capability Catalog

list_catalog

Read-onlyIdempotent

List services, products, external capabilities, or network metadata with optional filters. This is free and read-only; use discover_agents for a task-specific match and create_paid_job only after selecting a service.

Input Schema

Name	Required	Description	Default
`q`	No	Optional business or capability text used to filter catalog entries.
`limit`	No	Maximum number of entries returned in each selected catalog slice.
`filter`	No	Select the catalog slice to return.	all

Output Schema

Name	Required	Description
`filter`	No	Catalog slice used for the response.
`network`	No	Supported network capability metadata.
`external`	No	Published external capability metadata.
`products`	No	Productized workflow metadata.
`services`	No	First-party and published service metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of entries returned in each selected catalog slice."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Filtered, read-only catalog response.",
+  "properties": {
+    "external": {
+      "description": "Published external capability metadata.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "filter": {
+      "description": "Catalog slice used for the response.",
+      "type": "string"
+    },
+    "network": {
+      "additionalProperties": true,
+      "description": "Supported network capability metadata.",
+      "type": "object"
+    },
+    "products": {
+      "description": "Productized workflow metadata.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "services": {
+      "description": "First-party and published service metadata.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's 'read-only' restates that but adds the non-annotation fact that the call is free (no payment/challenge flow). The workflow ordering constraint around create_paid_job is also useful behavioral context. It stops short of describing pagination or slice-return 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?

Two sentences, no filler. The capability enumeration and the cost/read-only constraint are front-loaded before the alternative-tool routing, which is the right ordering for an agent deciding whether to call it.

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?

An output schema exists, so return values needn't be explained, and the three optional parameters are fully specified in schema. Annotations cover safety and idempotency. Minor gap: nothing about default behavior when no filter/query is supplied, though the limit default (50) and slice semantics are documented in the schema.

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%, so q, limit, and filter are already fully documented in the schema with defaults and bounds. The description's mention of 'optional filters' adds no syntax or semantics beyond that, so the 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 and enumerates the exact resource slices (services, products, external capabilities, network metadata) that map one-to-one onto the filter enum. It also names discover_agents as the contrasting tool, so an agent can distinguish browsing from task-matching without opening either schema.

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 describes the selection logic: this tool for free read-only listing, discover_agents for a task-specific match, and create_paid_job only after a service has been selected. That is a genuine when-to-use / when-to-use-something-else routing rule rather than implied usage.

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.