RugShield

get_job_result

Poll an accepted job for free. A paid job reports processing, ready, or failed without revealing its result before settlement; retry_after_s gives the next polling delay, capped at two minutes. An uncertain payment reports needs_review with no automatic retry: keep the job ID and contact support without another payment. After confirmed settlement, retrieve the saved result. Read agent_guidance.payment and agent_guidance.analysis separately. Legacy charged:null means unconfirmed, not free. Historical saved replies remain unchanged; this free status tool exposes current state explanations.

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID returned by a paid check or accepted queued request. Poll for status without another payment; a settled result is available here.

Output Schema

Name	Required	Description
`id`	No	Legacy opaque job identifier.
`code`	No	Error code when the tool cannot fulfill this request.
`kind`	No	Stored job kind when exposed; production paid checks use token_risk, tx_guard or risk_panel.
`error`	No
`eta_s`	No	Estimated queue delay, not a completion deadline.
`job_id`	No	Opaque server-returned job identifier; preserve it exactly.
`result`	No	Conditional result. Paid results are released only after confirmed settlement; token/transaction jobs expose the saved paid response envelope, while prepaid panels expose their analysis object when ready. Legacy non-purchase jobs may expose their result directly. Absence never proves no charge.
`status`	No	Analysis and payment are separate facts. ready/done can mean work finished while its paid result is still withheld; needs_review can concern payment or analysis. Read agent_guidance.payment and analysis.
`charged`	No	Legacy: true confirms settlement, false reports no settled charge for this attempt, null means unconfirmed. Never infer a refund or no charge from null.
`message`	No
`prepaid`	No
`created_at`	No
`status_url`	No	Free GET path for this existing job; no settlement or analysis restart.
`next_action`	No
`status_tool`	No	Free tool to observe the existing retry; normally get_job_result.
`instructions`	No
`retry_after_s`	No	Free polling delay, not a deadline or instruction to authorize payment.
`agent_guidance`	Yes	Optional additive agent instructions; does not replace x402 headers or the original result.
`delivery_state`	No	Legacy ledger state when returned by a job/retry observation.
`payment_status`	No	Legacy ledger or error field. Use agent_guidance.payment for the explicit charge outcome.
`receipt_header`	No	Stored receipt when available. This is not a new payment proof to authorize or replay.
`payment_receipt`	No	Decoded receipt when available after settlement; historical encoded receipts may remain only in receipt_header.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "status"
+      ]
+    },
+    {
+      "required": [
+        "code",
+        "message"
+      ]
+    }
+  ],
+  "description": "Free job observation or a tool error. Conditional fields preserve historical job variants. Paid panel failure can require analysis review even when payment is settled; payment and analysis are separate. Read agent_guidance.payment and analysis. A missing receipt or result does not prove no charge or refund.",
+  "properties": {
+    "agent_guidance": {
+      "description": "Optional additive agent instructions; does not replace x402 headers or the original result.",
+      "properties": {
+        "analysis": {
+          "properties": {
+            "explanation": {
+              "type": "string"
+            },
+            "result_available": {
+              "type": "boolean"
+            },
+            "status": {
+              "enum": [
+                "not_started",
+                "waiting_for_payment",
+                "queued",
+                "running",
+                "processing",
+                "completed",
+                "failed",
+                "review_required",
+                "not_reported"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "status",
+            "result_available",
+            "explanation"
+          ],
+          "type": "object"
+        },
+        "code": {
+          "type": "string"
+        },
+        "documentation": {
+          "type": "string"
+        },
+        "examples": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "instructions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "next_action": {
+          "type": "string"
+        },
+        "payment": {
+          "properties": {
+            "background_reconciliation_available": {
+              "const": false,
+              "type": "boolean"
+            },
+            "charge_outcome": {
+              "enum": [
+                "not_applicable",
+                "not_charged",
+                "charged",
+                "unconfirmed"
+              ],
+              "type": "string"
+            },
+            "explanation": {
+              "type": "string"
+            },
+            "legacy_charged_note": {
+              "type": "string"
+            },
+            "new_authorization_allowed": {
+              "type": "boolean"
+            },
+            "next_action": {
+              "type": "string"
+            },
+            "status": {
+              "enum": [
+                "not_required",
+                "not_started",
+                "not_settled",
+                "confirmation_pending",
+                "settled",
+                "reconciliation_required",
+                "unconfirmed"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "status",
+            "charge_outcome",
+            "explanation",
+            "next_action"
+          ],
+          "type": "object"
+        },
+        "payment_allowed": {
+          "description": "Advisory only; server preflight enforces input validity.",
+          "type": "boolean"
+        },
+        "payment_status": {
+          "enum": [
+            "settled",
+            "not_charged",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "request_example": {
+          "description": "Recommended NEXT action. A blueprint is not executable until its required original context or actual inputs are supplied. No signing or payment is performed by returning this object.",
+          "properties": {
+            "body_fields": {
+              "type": "object"
+            },
+            "effects": {
+              "properties": {
+                "analysis": {
+                  "enum": [
+                    "none",
+                    "read_operation_schema",
+                    "read_existing_job",
+                    "request_free_token_analysis",
+                    "read_advisor_catalog",
+                    "resume_or_recover_existing_job",
+                    "start_or_complete_analysis",
+                    "attempt_free_retry"
+                  ],
+                  "type": "string"
+                },
+                "payment": {
+                  "enum": [
+                    "none",
+                    "may_settle_original_authorization",
+                    "may_settle_reviewed_authorization"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "payment",
+                "analysis"
+              ],
+              "type": "object"
+            },
+            "executable": {
+              "type": "boolean"
+            },
+            "explanation": {
+              "type": "string"
+            },
+            "method": {
+              "type": "string"
+            },
+            "new_authorization_allowed": {
+              "type": "boolean"
+            },
+            "payment_proof_required": {
+              "type": "boolean"
+            },
+            "request_source": {
+              "type": "string"
+            },
+            "requires": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "type": {
+              "enum": [
+                "http",
+                "mcp",
+                "original_context",
+                "original_request",
+                "manual",
+                "none"
+              ],
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            },
+            "url_template": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "type",
+            "executable",
+            "explanation",
+            "effects",
+            "payment_proof_required",
+            "new_authorization_allowed"
+          ],
+          "type": "object"
+        },
+        "schema": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "charged": {
+      "description": "Legacy: true confirms settlement, false reports no settled charge for this attempt, null means unconfirmed. Never infer a refund or no charge from null.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "code": {
+      "description": "Error code when the tool cannot fulfill this request.",
+      "type": "string"
+    },
+    "created_at": {
+      "type": "number"
+    },
+    "delivery_state": {
+      "description": "Legacy ledger state when returned by a job/retry observation.",
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "eta_s": {
+      "description": "Estimated queue delay, not a completion deadline.",
+      "type": "number"
+    },
+    "id": {
+      "description": "Legacy opaque job identifier.",
+      "type": "string"
+    },
+    "instructions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "job_id": {
+      "description": "Opaque server-returned job identifier; preserve it exactly.",
+      "type": "string"
+    },
+    "kind": {
+      "description": "Stored job kind when exposed; production paid checks use token_risk, tx_guard or risk_panel.",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "next_action": {
+      "type": "string"
+    },
+    "payment_receipt": {
+      "description": "Decoded receipt when available after settlement; historical encoded receipts may remain only in receipt_header.",
+      "properties": {
+        "network": {
+          "type": "string"
+        },
+        "success": {
+          "type": "boolean"
+        },
+        "transaction": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "payment_status": {
+      "description": "Legacy ledger or error field. Use agent_guidance.payment for the explicit charge outcome.",
+      "enum": [
+        "reserved",
+        "prepared",
+        "claiming",
+        "uncertain",
+        "settled",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "prepaid": {
+      "type": "boolean"
+    },
+    "receipt_header": {
+      "description": "Stored receipt when available. This is not a new payment proof to authorize or replay.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "result": {
+      "description": "Conditional result. Paid results are released only after confirmed settlement; token/transaction jobs expose the saved paid response envelope, while prepaid panels expose their analysis object when ready. Legacy non-purchase jobs may expose their result directly. Absence never proves no charge."
+    },
+    "retry_after_s": {
+      "description": "Free polling delay, not a deadline or instruction to authorize payment.",
+      "minimum": 1,
+      "type": "integer"
+    },
+    "status": {
+      "description": "Analysis and payment are separate facts. ready/done can mean work finished while its paid result is still withheld; needs_review can concern payment or analysis. Read agent_guidance.payment and analysis.",
+      "enum": [
+        "awaiting_payment",
+        "queued",
+        "running",
+        "processing",
+        "done",
+        "ready",
+        "failed",
+        "payment_processing",
+        "needs_review"
+      ],
+      "type": "string"
+    },
+    "status_tool": {
+      "description": "Free tool to observe the existing retry; normally get_job_result.",
+      "type": "string"
+    },
+    "status_url": {
+      "description": "Free GET path for this existing job; no settlement or analysis restart.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "agent_guidance"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / job_id / description

Added value: +"Job ID returned by a paid check or accepted queued request. Poll for status without another payment; a settled result is available here."

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it is free and non-charging, paid jobs withhold results until settlement, retry_after_s is capped at two minutes, needs_review means uncertain payment with no automatic retry, and legacy charged:null means unconfirmed rather than free. These are exactly the non-obvious traits an agent would otherwise guess wrong on.

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

Conciseness4/5

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

Front-loaded with the core action and cost model, then layers state semantics. It is dense but mostly earns its sentences; the trailing 'Historical saved replies remain unchanged' clause is the weakest and reads as a caveat bolted onto an otherwise tight description.

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?

Covers the full polling lifecycle, all four payment/status outcomes, backoff behavior, and the needs_review escalation path, which is ample for a one-parameter tool. Return values are covered by the existing output schema, so the remaining gap is only that agent_guidance.payment and agent_guidance.analysis are referenced without saying what each contains.

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 coverage is 100% and the single job_id parameter is already documented in the schema as coming from a paid check or accepted queued request. The description reinforces the 'poll without another payment' lifecycle but never names or adds syntax to job_id, so the schema does the work and baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Poll an accepted job') plus its economic scope ('for free'), and immediately distinguishes it from the paid path by noting a paid job won't reveal its result before settlement. An agent can tell this apart from retry_failed_job and the paid check tools without opening a schema.

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?

Gives concrete when-to-use guidance: poll while processing, back off per retry_after_s, retrieve the saved result only after confirmed settlement, and on needs_review keep the job ID and contact support rather than paying again. It stops short of naming retry_failed_job as the alternative when a job has failed, leaving that routing implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RugShield tools Inspect

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

Need Help?