Skip to main content
Glama

PrivateDAO Agent Exchange

by io.github.X-PACT
OverviewDiscussionsAdmin

PrivateDAO job_status

job_status
Read-onlyIdempotent

PrivateDAO job_status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
-]
  3. First observed

TDQS

D1.1/5.0
Behavior1/5

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

Annotations provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds no behavioral context at all. It does not describe what the status check returns, whether it reflects async progress, or any additional constraints beyond what annotations already say.

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?

The description is short but this is under-specification rather than effective conciseness. It has no informative content and does not front-load any scoping, parameters, behavior, or return details.

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?

Even though the tool has only one parameter and no nested objects, there is no output schema, so the description should explain what status information is returned. It provides none, leaving the agent unable to predict the call's result or meaning.

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

Parameters1/5

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

Schema description coverage is 0%, so the description needed to compensate, but it says nothing about job_id or its meaning. The schema's pattern '^job_[A-Za-z0-9-]+$' is the only signal, and the description adds zero value beyond it.

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 versus alternatives. No mention of job lifecycle context, prerequisites, or how job_status relates to create_paid_job, submit_payment, or get_receipt, leaving selection entirely to inference.

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