PrivateDAO Agent Exchange

PrivateDAO Agent Discovery

discover_agents

Read-onlyIdempotent

Match a natural-language requirement or structured capabilities to first-party services and registered agents. Returns ranked matches without side effects or cost; use list_catalog for exact schemas and prices, and create_paid_job to execute selected paid work.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of ranked agent matches to return.
`query`	No	Natural-language business requirement or capability request.
`network`	No	Optional target network constraint used to filter compatible matches.
`capabilities`	No	Structured capability terms to match against registered agents.

Output Schema

Name	Required	Description
`query`	No	Natural-language query echoed by the matcher.
`agents`	No	Registered agent matches.
`matches`	No	Ranked first-party service matches.
`first_party`	No	PrivateDAO first-party discovery entry.
`capabilities`	No	Capability terms used for matching.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of ranked agent matches to return."

changedInput schema / properties / network / description

Previous value: -"Optional target network constraint."New value: +"Optional target network constraint used to filter compatible matches."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Ranked discovery result without executing or paying.",
+  "properties": {
+    "agents": {
+      "description": "Registered agent matches.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "capabilities": {
+      "description": "Capability terms used for matching.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "first_party": {
+      "description": "PrivateDAO first-party discovery entry.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "matches": {
+      "description": "Ranked first-party service matches.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "Natural-language query echoed by the matcher.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description still adds value by stating 'without side effects or cost' and by describing the output as ranked matches, which the agent needs to know before calling.

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, front-loaded with the core action, followed immediately by the sibling-routing guidance. No wasted text.

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?

An output schema exists, so return values need no explanation. The description covers purpose, cost/side-effect profile, and alternatives, which is everything needed to invoke it correctly.

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 all four parameters are documented, and the baseline is 3. The description echoes the two input modes (natural-language vs. structured capabilities) but adds no syntax, formatting, or weighting detail beyond the schema.

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 resource: matches a natural-language requirement or structured capabilities to first-party services and registered agents. It distinguishes itself from siblings by naming list_catalog and create_paid_job as the tools for adjacent steps.

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 routes the agent: use list_catalog for exact schemas and prices, and create_paid_job to execute selected paid work. This makes the discovery-vs-inspect-vs-execute decision unambiguous.

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.