Skip to main content
Glama
Sign In

PrivateDAO Agent Exchange

by io.github.X-PACT
OverviewDiscussionsAdmin

PrivateDAO Capability Advisor

service_recommendation
Read-onlyIdempotent

Translate a business or product objective into the most relevant PrivateDAO capabilities and a practical next step.

Input Schema

NameRequiredDescriptionDefault
taskYesNatural-language task the agent wants to accomplish.
networkNoOptional target network constraint.

Output Schema

NameRequiredDescriptionDefault
noteNoMatching and next-step guidance.
taskNoThe original business task.
matchesNoRanked service manifests to inspect before requesting work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • changedOutput schema / description
      Previous value: -"Structured PrivateDAO tool response."New value: +"Ranked first-party service recommendations for the requested business task."
    • addedOutput schema / properties
      Added value: +{
+  "matches": {
+    "description": "Ranked service manifests to inspect before requesting work.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "note": {
+    "description": "Matching and next-step guidance.",
+    "type": "string"
+  },
+  "task": {
+    "description": "The original business task.",
+    "type": "string"
+  }
+}
  6. Added
  7. Removed
  8. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds that the tool returns relevant capabilities and a practical next step, but because an output schema exists, this adds only modest behavioral context beyond structured fields.

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?

A single front-loaded sentence with no waste. It states the transformation and outcome efficiently.

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?

The tool is simple (2 parameters, output schema present, rich annotations), and the description sufficiently conveys that it is a recommendation/advisor tool producing capabilities and a next step. It could more explicitly state that it does not execute actions or when to prefer it over concrete sibling tools, but the essentials are present.

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 the schema fully documents the 'task' and optional 'network' parameters. The description adds no extra meaning about parameter syntax, format, or constraints, which is acceptable given the complete schema.

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 uses a specific verb ('Translate') and resource ('PrivateDAO capabilities') and clearly frames the tool as an advisor that maps objectives to recommendations. It does not explicitly distinguish itself from siblings like get_workflow_guide or list_catalog, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a business or product objective needing capability mapping, but it gives no explicit when-to-use, when-not-to-use, or alternative tools. The agent must infer this is an entry point rather than a concrete operation.

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