MCP Server for Wave

Wave: Auth Status

wave_auth_status

Read-onlyIdempotent

Check Wave credential resolution status and write tool availability without making an API request. Use it first to diagnose authentication errors even if the token is missing or expired.

Instructions

Report how this server resolved its Wave credentials and whether write tools are enabled. Makes no Wave API request, so it works even when the token is missing or expired -- use it first when other tools report authentication problems.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next_step`	No
`token_source`	Yes
`lookup_errors`	Yes
`detected_agent`	Yes
`writes_enabled`	Yes
`has_credentials`	Yes
`sources_checked`	Yes
`registered_tools`	Yes
`write_tools_hidden`	Yes
`default_business_id`	Yes
`config_fallback_disabled`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.8Sep 24, 2026
- removedOutput schema / properties / default_business_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / default_business_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / sources_checked / items / properties / path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / sources_checked / items / properties / path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / token_source / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / token_source / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedv1.0.6Aug 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "config_fallback_disabled": {
+      "type": "boolean"
+    },
+    "default_business_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "detected_agent": {
+      "type": "string"
+    },
+    "has_credentials": {
+      "type": "boolean"
+    },
+    "lookup_errors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "registered_tools": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "sources_checked": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "found": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "path": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "path",
+          "found"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "token_source": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "write_tools_hidden": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "writes_enabled": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "has_credentials",
+    "token_source",
+    "writes_enabled",
+    "default_business_id",
+    "detected_agent",
+    "config_fallback_disabled",
+    "sources_checked",
+    "lookup_errors",
+    "registered_tools",
+    "write_tools_hidden"
+  ],
+  "type": "object"
+}

First observedv1.0.2Jul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description adds valuable behavioral context beyond the annotations: it makes no network request to Wave and remains functional when credentials are invalid. This directly helps an agent understand failure modes and when to trust the tool's output.

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 tightly written sentences with the core purpose front-loaded and the usage guidance in the second sentence. No filler or repetition of schema or annotation information.

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 zero-parameter diagnostic tool with an output schema, the description covers what it reports, its offline behavior, the token-failure scenario, and when to invoke it. There are no missing operational details an agent would need.

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, so there is nothing for the description to clarify beyond the empty schema. The baseline of 4 for a zero-parameter tool is appropriate, and the description's focus on output semantics is fine.

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 states a specific diagnostic purpose: report how the server resolved Wave credentials and whether write tools are enabled. This clearly distinguishes it from the many data-oriented sibling tools such as wave_get_user or wave_list_invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit usage directive: use it first when other tools report authentication problems. It also explains why it is appropriate in that situation by noting it makes no Wave API request and works despite missing or expired tokens.

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