run402-mcp

Overview Schema Source Related Servers Discussions Admin

whoami

Retrieve the remote control-plane identity for this server's wallet, including active authenticator, linked identities, org memberships, and sign-in session grade. Use status for the local wallet.

Instructions

The remote identity (r.orgs.whoami()): the control-plane principal this server's wallet resolves to, its active authenticator and linked identities, its org memberships, and the sign-in session grade (none for a wallet). For the local wallet use status. Any other operation is a run snippet against r, the Node SDK client; docs is its reference.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv4.126.1Oct 22, 2026

addedOutput schema / properties / error / properties / diagnostics

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "column": {
+        "type": "integer"
+      },
+      "line": {
+        "type": "integer"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "line",
+      "column",
+      "code",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / error / properties / diagnostics_ref
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / error / properties / diagnostics_total
```
Added value: +{
+  "type": "integer"
+}
```

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": {
+        "memberships": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "org_id": {
+                "type": "string"
+              },
+              "role": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "org_id"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "principal": {
+          "additionalProperties": true,
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id"
+          ],
+          "type": "object"
+        },
+        "session": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "grade": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "principal",
+        "memberships"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "error"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv3.6.0Jun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned identity facets and notes the session grade is 'none for a wallet,' which is useful, but it doesn't state whether authentication is required or how it behaves when unauthenticated.

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?

The core purpose is front-loaded in the first clause, followed by the return facets and sibling routing. The `run`/`docs` sentence is slightly tangential but earns its place as routing context.

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?

An output schema exists, so return values needn't be re-explained, and with no parameters the main remaining need is purpose and sibling routing, both covered. The only gap is the lack of auth/error behavior disclosure for a tool with no annotations.

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 takes zero parameters, so there is nothing for the description to clarify. Baseline 4 applies for a parameterless tool.

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?

The description enumerates exactly what the tool returns: the control-plane principal, active authenticator, linked identities, org memberships, and session grade. It distinguishes itself from the sibling `status`, which handles the local wallet, so an agent can tell the two apart without opening schemas.

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 routes the local-wallet case to `status` and states that any other operation should be a `run` snippet against `r`, with `docs` as its reference. It gives clear positive and negative guidance, though it doesn't spell out error/unauthenticated conditions.

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

Deploy Server