ExpenseBot

get_spending_summary

Read-only

Summarize the user's recorded expenses with totals and breakdowns by category, merchant, month, tag, source, or payment method. Supports date ranges, period comparisons, and total, count, or average metrics. Read-only. Returns: { message, data: { total, breakdown?, comparison?, sampleMeta? } }.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Natural language question (e.g., 'how much did I spend in March', 'top merchants this quarter')
`metric`	No
`groupBy`	No
`dateRange`	No	Time period filter. Use exactly one variant — pick the shape that matches the user's phrasing.
`categories`	No	Optional configured expense categories to include in the summary.
`clientEmail`	No	Client account email. Accountants may use this only for an accepted ExpenseBot client.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Inline branch: computed analytics, or null when no spreadsheet / no data.
`type`	No	Async branch only: "analytics_pending" — poll pollEndpoint or call poll_analytics with jobId.
`jobId`	No	Async branch only.
`message`	No	Human-readable narrative (both branches).
`success`	No	Async branch only.
`response`	No	Chat alias of message.
`pollEndpoint`	No	Async branch only.
`pollInterval`	No	Async branch only: milliseconds.
`estimatedTime`	No	Async branch only: seconds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Two branches. Async: type='analytics_pending' with jobId — poll poll_analytics until complete. Inline: message + data with the computed analytics (data may be null when there is no spreadsheet or no data yet). success is present only on the async branch.",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Inline branch: computed analytics, or null when no spreadsheet / no data.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "estimatedTime": {
+      "description": "Async branch only: seconds.",
+      "type": "number"
+    },
+    "jobId": {
+      "description": "Async branch only.",
+      "type": "string"
+    },
+    "message": {
+      "description": "Human-readable narrative (both branches).",
+      "type": "string"
+    },
+    "pollEndpoint": {
+      "description": "Async branch only.",
+      "type": "string"
+    },
+    "pollInterval": {
+      "description": "Async branch only: milliseconds.",
+      "type": "number"
+    },
+    "response": {
+      "description": "Chat alias of message.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Async branch only.",
+      "type": "boolean"
+    },
+    "type": {
+      "description": "Async branch only: \"analytics_pending\" — poll pollEndpoint or call poll_analytics with jobId.",
+      "type": "string"
+    }
+  },
+  "required": [],
+  "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

Changed1 schema field changedAug 22, 2026
- addedInput schema / properties / categories / description
```
Added value: +"Optional configured expense categories to include in the summary."
```
First observedAug 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds a compact return shape ('Returns: { message, data: { total, breakdown?, comparison?, sampleMeta? } }'), which gives some behavioral context beyond annotations. It does not describe auth requirements, rate limits, or edge cases, but the annotations cover the important safety dimension.

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 three sentences long, front-loaded with the core capability, then covering options, read-only status, and return shape. There is no filler or redundant elaboration; every clause contributes to an agent's understanding.

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?

After accounting for the existing output schema and annotations, the description fills the main gap by documenting the enum parameters and the overall purpose. It lacks context about natural-language query usage (e.g., that query can be a free-form question) and does not mention the clientEmail restriction, but these are already in the schema. The main omitted guidance about which sibling to use instead is captured in the usage_guidelines dimension.

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?

Schema description coverage is 67%, and the two undocumented parameters (metric and groupBy) are clear from the description: it lists 'category, merchant, month, tag, source, or payment method' and 'total, count, or average metrics', mapping directly to the enum values. This adds real semantics beyond the schema. Other params (query, dateRange, categories, clientEmail) are adequately described in the schema.

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 states a specific verb and resource: 'Summarize the user's recorded expenses with totals and breakdowns...' It also enumerates grouping dimensions and metrics, making the intent concrete. It does not explicitly name sibling alternatives like get_income_summary or get_pnl, but the 'expenses' scope and read-only nature implicitly distinguish it from those.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is given. The description mentions capabilities ('Supports date ranges, period comparisons...') but does not clarify when to choose this rather than sibling tools like get_income_summary, get_pnl, or get_deep_analytics. With a large sibling list, the absence of route-to-alternative guidance is a significant gap.

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.