Skip to main content
Glama

PrivateDAO Agent Exchange

by io.github.X-PACT
OverviewDiscussionsAdmin

PrivateDAO agent_match

agent_match
Read-onlyIdempotent

Free registry discovery and capability matching. Use create_paid_job for the paid agent.match service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoCanonical network or accepted alias.
capabilitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "capabilities": {
+    "items": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "maxItems": 32,
+    "type": "array"
+  },
+  "network": {
+    "description": "Canonical network or accepted alias.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "capabilities"
+]
  2. Changed2 schema fields changed
    • removedInput schema / properties
      Removed value: -{
-  "capabilities": {
-    "items": {
-      "maxLength": 120,
-      "type": "string"
-    },
-    "maxItems": 32,
-    "type": "array"
-  },
-  "network": {
-    "description": "Canonical network or accepted alias.",
-    "type": "string"
-  }
-}
    • removedInput schema / required
      Removed value: -[
-  "capabilities"
-]
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well established. The description adds only the 'free registry discovery and capability matching' framing, with no detail on rate limits, result behavior, or matching semantics.

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 short sentences carry the entire definition: one states what the tool does, the other names the paid alternative. There is no filler, and the key free-vs-paid distinction is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is workable for a simple read-only tool, especially with rich annotations. However, there is no output schema and the description does not explain what the tool returns or how it differs from search_agents, leaving meaningful gaps in a crowded 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?

The network parameter is documented in the schema, but the capabilities parameter has no schema description. The phrase 'capability matching' gives capabilities a clear purpose, yet it does not explain matching rules or the expected format, leaving 50% schema coverage only partially compensated.

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?

The description states a specific purpose: free registry discovery and capability matching. It clearly distinguishes itself from the paid create_paid_job service, but does not differentiate from the similar-sounding sibling search_agents.

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?

The description explicitly says to use create_paid_job for the paid agent.match service, giving a clear when-not-to-use condition. However, it provides no guidance relative to other free siblings like search_agents, so the usage guidance is only partial.

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 toolsInspect
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.

Resources