Skip to main content
Glama

PrivateDAO Agent Exchange

by io.github.X-PACT
OverviewDiscussionsAdmin

PrivateDAO create_paid_job

create_paid_job

PrivateDAO create_paid_job

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoService-specific JSON input.
service_idYes
pdao_accessNoOptional signed PDAO holder challenge from /api/access/challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_id / enum
      Previous value: -[
-  "verify.deep",
-  "token.intelligence",
-  "risk.score",
-  "wallet.intelligence",
-  "contract.inspect",
-  "launch.check",
-  "market.snapshot",
-  "research.asset",
-  "research.wallet",
-  "contract.explain",
-  "transaction.explain",
-  "anomaly.detect",
-  "agent.research.report",
-  "portfolio.intelligence",
-  "swap.quote",
-  "transaction.simulate",
-  "decision.context",
-  "github.repository",
-  "forensics.trace",
-  "agent.match",
-  "sponsored.discovery",
-  "intelligence.synthesize"
-]New value: +[
+  "verify.deep",
+  "token.intelligence",
+  "risk.score",
+  "wallet.intelligence",
+  "wallet.bot.classify",
+  "contract.inspect",
+  "launch.check",
+  "market.snapshot",
+  "research.asset",
+  "research.wallet",
+  "contract.explain",
+  "transaction.explain",
+  "anomaly.detect",
+  "agent.research.report",
+  "portfolio.intelligence",
+  "swap.quote",
+  "transaction.simulate",
+  "decision.context",
+  "github.repository",
+  "forensics.trace",
+  "agent.match",
+  "sponsored.discovery",
+  "intelligence.synthesize"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / pdao_access
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional signed PDAO holder challenge from /api/access/challenge.",
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "signature": {
+      "type": "string"
+    },
+    "wallet": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "wallet",
+    "message",
+    "signature",
+    "nonce"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / service_id / enum
      Previous value: -[
-  "verify.deep",
-  "token.intelligence",
-  "risk.score",
-  "wallet.intelligence",
-  "contract.inspect",
-  "launch.check",
-  "market.snapshot",
-  "research.asset",
-  "research.wallet",
-  "contract.explain",
-  "transaction.explain",
-  "anomaly.detect",
-  "agent.research.report",
-  "portfolio.intelligence",
-  "swap.quote",
-  "transaction.simulate",
-  "decision.context",
-  "forensics.trace",
-  "agent.match",
-  "sponsored.discovery",
-  "intelligence.synthesize"
-]New value: +[
+  "verify.deep",
+  "token.intelligence",
+  "risk.score",
+  "wallet.intelligence",
+  "contract.inspect",
+  "launch.check",
+  "market.snapshot",
+  "research.asset",
+  "research.wallet",
+  "contract.explain",
+  "transaction.explain",
+  "anomaly.detect",
+  "agent.research.report",
+  "portfolio.intelligence",
+  "swap.quote",
+  "transaction.simulate",
+  "decision.context",
+  "github.repository",
+  "forensics.trace",
+  "agent.match",
+  "sponsored.discovery",
+  "intelligence.synthesize"
+]
  4. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "input": {
+    "description": "Service-specific JSON input.",
+    "type": "object"
+  },
+  "service_id": {
+    "enum": [
+      "verify.deep",
+      "token.intelligence",
+      "risk.score",
+      "wallet.intelligence",
+      "contract.inspect",
+      "launch.check",
+      "market.snapshot",
+      "research.asset",
+      "research.wallet",
+      "contract.explain",
+      "transaction.explain",
+      "anomaly.detect",
+      "agent.research.report",
+      "portfolio.intelligence",
+      "swap.quote",
+      "transaction.simulate",
+      "decision.context",
+      "forensics.trace",
+      "agent.match",
+      "sponsored.discovery",
+      "intelligence.synthesize"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "service_id"
+]
  5. Changed2 schema fields changed
    • removedInput schema / properties
      Removed value: -{
-  "input": {
-    "description": "Service-specific JSON input.",
-    "type": "object"
-  },
-  "service_id": {
-    "enum": [
-      "verify.deep",
-      "token.intelligence",
-      "risk.score",
-      "wallet.intelligence",
-      "contract.inspect",
-      "launch.check",
-      "market.snapshot",
-      "research.asset",
-      "research.wallet",
-      "contract.explain",
-      "transaction.explain",
-      "anomaly.detect",
-      "agent.research.report",
-      "portfolio.intelligence",
-      "swap.quote",
-      "transaction.simulate",
-      "decision.context",
-      "forensics.trace",
-      "agent.match",
-      "sponsored.discovery",
-      "intelligence.synthesize"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / required
      Removed value: -[
-  "service_id"
-]
  6. First observed

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false, and destructiveHint=false, but the description adds nothing beyond them — no mention of cost, payment implications, auth requirements, or what a job creation entails. With annotations carrying the entire safety profile, the description contributes zero additional behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At four words it is short, but this is under-specification rather than conciseness. Nothing is front-loaded because nothing meaningful is said.

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

Completeness1/5

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

This is a mutating, non-idempotent creation tool with a nested authentication object (wallet/message/signature/nonce), an enum of 23 service IDs, no output schema, and no guidance on payment semantics. The description leaves every one of these gaps unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is a middling 67%, covering 'input' and 'pdao_access' while the description explains none of the three parameters. It does not clarify what service_id values mean, what service-specific JSON shape 'input' expects, or that pdao_access is an optional signed holder challenge — so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no guidance about when to use this tool, when not to, or which sibling handles adjacent tasks. An agent has no basis for routing between create_paid_job and submit_payment or logistics_request.

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