ExpenseBot

get_scan_status

Read-only

Check authoritative Gmail receipt scan status. Returns the active lock and live phase/progress shown in-app, queued or attention-needed periods, completed calendar years, and tax-period statuses with their returned labels and inclusive ISO bounds, plus exclusions and recent outcomes. Use when asked if a scan is running, finished, stuck, or what it is doing. On completion show spreadsheetUrl or reviewExpensesUrl; for setup/reconnection show gmailScanUrl. Read-only.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`data`	No
`lock`	No	Scan-lock state (active, startedAt, ageSeconds, dispatchComplete, pendingProcessingCount).
`status`	No	Scan lifecycle state.
`message`	No
`success`	Yes
`latestScan`	No	Most recent scan outcome (success, emailsFound, emailsTagged, timestamp).
`gmailScanUrl`	No
`scanInProgress`	No
`spreadsheetUrl`	No
`reviewExpensesUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / description

Previous value: -"Authoritative live scan state. Fields may sit at the top level or under data depending on the branch; nothing beyond success is guaranteed, so treat each as optional."New value: +"Authoritative live scan state. Fields may be top-level or under data; only success is guaranteed, so treat the rest as optional."

Changed5 schema fields changedSep 9, 2026

changedOutput schema / properties / gmailScanUrl / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / latestScan / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / reviewExpensesUrl / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / spreadsheetUrl / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / status / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Authoritative live scan state. Fields may sit at the top level or under data depending on the branch; nothing beyond success is guaranteed, so treat each as optional.",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "gmailScanUrl": {
+      "type": "string"
+    },
+    "latestScan": {
+      "additionalProperties": true,
+      "description": "Most recent scan outcome (success, emailsFound, emailsTagged, timestamp).",
+      "type": "object"
+    },
+    "lock": {
+      "additionalProperties": true,
+      "description": "Scan-lock state (active, startedAt, ageSeconds, dispatchComplete, pendingProcessingCount).",
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "reviewExpensesUrl": {
+      "type": "string"
+    },
+    "scanInProgress": {
+      "type": "boolean"
+    },
+    "spreadsheetUrl": {
+      "type": "string"
+    },
+    "status": {
+      "description": "Scan lifecycle state.",
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
-  "properties": {
-    "data": {
-      "additionalProperties": true,
-      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
-      "type": "object"
-    },
-    "error": {
-      "additionalProperties": true,
-      "description": "Present only when success === false.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "hint": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "message": {
-      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
-      "type": "string"
-    },
-    "sampleMeta": {
-      "additionalProperties": true,
-      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
-      "properties": {
-        "isTruncated": {
-          "type": "boolean"
-        },
-        "sampleCount": {
-          "type": "integer"
-        },
-        "totalCount": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "success": {
-      "description": "False on tool errors; check before reading `data`.",
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null

First observedAug 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral detail beyond that, including live phase/progress, queued/attention-needed periods, exclusions, recent outcomes, and which URL to surface after completion versus setup/reconnection.

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 description is front-loaded with purpose and then usage triggers. It is somewhat dense and lists many return fields even though an output schema exists, but the routing guidance is valuable and most sentences earn their place.

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?

With zero parameters, an output schema present, and annotations covering safety, the description is complete enough for correct invocation. It explains what kind of status is returned and how to route the user to the appropriate URL afterward.

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?

There are zero parameters, so no parameter semantics are needed. The baseline for a parameterless tool is 4.

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 verb and resource ('Check authoritative Gmail receipt scan status') and clearly separates this status tool from scan-triggering or receipt-processing siblings. It also names the domain object ('Gmail receipt scan') precisely.

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?

It gives explicit usage triggers: asked whether a scan is running, finished, stuck, or what it is doing. It does not explicitly name alternatives such as scan_gmail or get_last_receipt_result, but the intended context is clear.

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

All ExpenseBot 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.