Skip to main content
Glama
Sign In

PrivateDAO Agent Exchange

by io.github.X-PACT
OverviewDiscussionsAdmin

PrivateDAO Request Status

job_status
Read-onlyIdempotent

Read the current state, exact payment intent, result, or receipt reference for a request. Poll this after create_paid_job, privatepay_job_payment, or submit_payment; it is free and read-only, never retries payment, and never executes work again.

Input Schema

NameRequiredDescriptionDefault
job_idYesJob identifier returned by create_paid_job; polling never retries or charges payment.

Output Schema

NameRequiredDescriptionDefault
job_idNoStable request identifier.
resultNoService result when complete.
statusNoCurrent request state.
receipt_idNoReceipt identifier when available.
payment_intentNoExact quote when payment is pending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Read the current asynchronous request state, exact payment intent, result, or receipt reference. This is free and never retries or charges a payment."
    • addedInput schema / properties / job_id / description
      Added value: +"Job identifier returned by create_paid_job; polling never retries or charges payment."
  2. Changed2 schema fields changed
    • removedInput schema / description
      Removed value: -"Read the current asynchronous request state, exact payment intent, result, or receipt reference. This is free and never retries or charges a payment."
    • removedInput schema / properties / job_id / description
      Removed value: -"Job identifier returned by create_paid_job; polling never retries or charges payment."
  3. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Read the current asynchronous request state, exact payment intent, result, or receipt reference. This is free and never retries or charges a payment."
    • addedInput schema / properties / job_id / description
      Added value: +"Job identifier returned by create_paid_job; polling never retries or charges payment."
  4. Changed2 schema fields changed
    • removedInput schema / description
      Removed value: -"Read the current asynchronous request state, exact payment intent, result, or receipt reference. This is free and never retries or charges a payment."
    • removedInput schema / properties / job_id / description
      Removed value: -"Job identifier returned by create_paid_job; polling never retries or charges payment."
  5. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Read the current asynchronous request state, exact payment intent, result, or receipt reference. This is free and never retries or charges a payment."
    • addedInput schema / properties / job_id / description
      Added value: +"Job identifier returned by create_paid_job; polling never retries or charges payment."
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Current read-only request state and available evidence.",
+  "properties": {
+    "job_id": {
+      "description": "Stable request identifier.",
+      "type": "string"
+    },
+    "payment_intent": {
+      "additionalProperties": true,
+      "description": "Exact quote when payment is pending.",
+      "type": "object"
+    },
+    "receipt_id": {
+      "description": "Receipt identifier when available.",
+      "type": "string"
+    },
+    "result": {
+      "additionalProperties": true,
+      "description": "Service result when complete.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Current request state.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  7. Changed2 schema fields changed
    • addedInput schema / properties
      Added value: +{
+  "job_id": {
+    "pattern": "^job_[A-Za-z0-9-]+$",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "job_id"
+]
  8. Changed2 schema fields changed
    • removedInput schema / properties
      Removed value: -{
-  "job_id": {
-    "pattern": "^job_[A-Za-z0-9-]+$",
-    "type": "string"
-  }
-}
    • removedInput schema / required
      Removed value: -[
-  "job_id"
-]
  9. First observed

TDQS

A4.1/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. The description usefully reinforces this by stating it is free, never retries payment, and never re-executes work — meaningful safety context for a polling tool beyond the annotations.

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 tight sentences with zero waste; the core purpose and the safety reassurance are front-loaded, and the usage cue follows immediately.

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?

With an output schema present, the description needn't explain return values, and it covers purpose, usage timing, and the non-charging/non-retry guarantee. Nothing an agent needs to call it correctly is missing.

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?

Only one parameter with 100% schema description coverage, so the schema already documents job_id, its pattern, and its origin. The description adds no syntax or format detail beyond what the schema and its field description already provide, so baseline 3 applies.

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?

States a specific verb (Read) and resource (current state, payment intent, result, receipt reference for a request), and ties it to prior creation/payment tools. It doesn't clarify how it differs from the sibling privatepay_status, leaving some ambiguity about which status tool to call.

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?

Explicitly says when to use it: 'Poll this after create_paid_job, privatepay_job_payment, or submit_payment.' That is clear context for invocation. It stops short of an exclusion vs privatepay_status, so routing between the two status tools is left partly implicit.

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