run402-mcp

Overview Schema Source Related Servers Discussions Admin

status

Check the current state of your AI-native Postgres account: wallet address, tier, lease, allowance, projects, and active project.

Instructions

The organization's state as this server's wallet sees it (r.status()): the wallet's local_label, server_label, and address, the tier and its lease, the allowance, the projects, and the active project. Never key material. Any other operation is a run snippet against r, the Node SDK client; docs is its reference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`result`	No
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "code": {
+          "type": "string"
+        },
+        "column": {
+          "type": "integer"
+        },
+        "details": {},
+        "fix": {},
+        "http_status": {
+          "type": "integer"
+        },
+        "line": {
+          "type": "integer"
+        },
+        "logs": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "message": {
+          "type": "string"
+        },
+        "mutation_state": {
+          "type": "string"
+        },
+        "next_actions": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "operation_id": {
+          "type": "string"
+        },
+        "phase": {
+          "type": "string"
+        },
+        "plan_id": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "safe_to_retry": {
+          "type": "boolean"
+        },
+        "trace_id": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "next_actions"
+      ],
+      "type": "object"
+    },
+    "result": {
+      "additionalProperties": true,
+      "properties": {
+        "active_project": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "projects": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "project_id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "project_id"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "tier": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "expires": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "name": {
+                  "type": "string"
+                },
+                "status": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "name",
+                "status",
+                "expires"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "wallet": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "address": {
+                  "type": "string"
+                },
+                "local_label": {
+                  "type": "string"
+                },
+                "server_label": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "local_label",
+                "address"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "wallet",
+        "projects",
+        "active_project"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "error"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv3.6.0Jun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description must bear the full burden. It discloses a critical behavioral trait: 'Never key material' – a security guarantee that agents can rely on. It also describes the perspective ('as this server's wallet sees it') and lists exact fields, but it does not explicitly state whether the operation is mutation-free or describe error conditions. Given the simplicity of a status call, this is adequate additional context over a bare name.

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?

The description is compact and front-loaded: it states the purpose in the first sentence, lists included fields, adds a security note, and then gives routing guidance for other operations. Every sentence adds value, and nothing is redundant. The structure makes it easy for an agent to quickly grasp what the tool does and what it doesn't do.

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?

For a simple, parameterless tool with an output schema available, the description is complete. It details the content of the state, excludes key material, and explains how it fits into the broader server API (via run and docs). No crucial information an agent would need to call this tool correctly is missing.

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

Parameters4/5

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

The tool has zero parameters, and the input schema is an empty object. Per the rubric, the baseline for 0 parameters is 4. The description does not need to explain any parameters, and it adds no parameter-related information, which is appropriate. It does not compensate for anything because there is nothing to compensate for.

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?

The description clearly states the tool returns the organization's state as the server's wallet sees it (r.status()), listing specific fields (local_label, server_label, address, tier, lease, allowance, projects, active project). It explicitly notes it never returns key material, distinguishing it from potential secret-retrieval operations. It also differentiates from siblings by stating any other operation is a 'run' snippet, so an agent knows this is the dedicated status 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?

The description gives a clear when-to-use signal: this tool is the status operation. It also provides an explicit exclusion: 'Any other operation is a run snippet', which routes agents to the run tool for other tasks. It references 'docs' for the SDK reference, but it does not compare directly with sibling tools like whoami or deploy, so it's clear but not exhaustive.

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

Deploy Server