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

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 matching the user's phrasing.
`categories`	No	Optional configured expense categories to include in the summary.
`clientEmail`	No	Accepted client's account email (accountants only).

Output 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.

Changed4 schema fields changedOct 27, 2026

changedInput schema / properties / clientEmail / description

Previous value: -"Client account email. Accountants may use this only for an accepted ExpenseBot client."New value: +"Accepted client's account email (accountants only)."

changedInput schema / properties / dateRange / description

Previous value: -"Time period filter. Use exactly one variant — pick the shape that matches the user's phrasing."New value: +"Time period filter; use exactly one variant matching the user's phrasing."

changedInput schema / properties / dateRange / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "month": {
-        "description": "Month name or 1-12 (e.g., 'March' or '3')",
-        "type": "string"
-      },
-      "type": {
-        "const": "month",
-        "type": "string"
-      },
-      "year": {
-        "description": "4-digit year (e.g., 2026)",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "month",
-      "year"
-    ],
-    "title": "Specific month",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "quarter": {
-        "maximum": 4,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "type": {
-        "const": "quarter",
-        "type": "string"
-      },
-      "year": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "quarter",
-      "year"
-    ],
-    "title": "Quarter of a year",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "year",
-        "type": "string"
-      },
-      "year": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "year"
-    ],
-    "title": "Full year",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "end": {
-        "description": "ISO date YYYY-MM-DD (inclusive)",
-        "format": "date",
-        "type": "string"
-      },
-      "start": {
-        "description": "ISO date YYYY-MM-DD (inclusive)",
-        "format": "date",
-        "type": "string"
-      },
-      "type": {
-        "const": "specific",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "start",
-      "end"
-    ],
-    "title": "Specific date range",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "relative",
-        "type": "string"
-      },
-      "value": {
-        "description": "Relative range phrase, e.g., 'last month', 'YTD', 'this quarter', 'last 7 days'",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "value"
-    ],
-    "title": "Relative natural-language range",
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "month": {
+        "description": "Month name or 1-12 (e.g., 'March' or '3')",
+        "type": "string"
+      },
+      "type": {
+        "const": "month",
+        "type": "string"
+      },
+      "year": {
+        "description": "4-digit year (e.g., 2026)",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "month",
+      "year"
+    ],
+    "title": "Specific month",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "quarter": {
+        "maximum": 4,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "type": {
+        "const": "quarter",
+        "type": "string"
+      },
+      "year": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "quarter",
+      "year"
+    ],
+    "title": "Quarter of a year",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "year",
+        "type": "string"
+      },
+      "year": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "year"
+    ],
+    "title": "Full year",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "ISO date YYYY-MM-DD (inclusive)",
+        "format": "date",
+        "type": "string"
+      },
+      "start": {
+        "description": "ISO date YYYY-MM-DD (inclusive)",
+        "format": "date",
+        "type": "string"
+      },
+      "type": {
+        "const": "specific",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "start",
+      "end"
+    ],
+    "title": "Specific date range",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "relative",
+        "type": "string"
+      },
+      "value": {
+        "description": "Relative phrase, e.g. 'last month', 'YTD', 'last 7 days'",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "value"
+    ],
+    "title": "Relative natural-language range",
+    "type": "object"
+  }
+]

changedOutput schema / description

Previous value: -"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."New value: +"Async: type='analytics_pending' with jobId (poll poll_analytics). Inline: message + data (data may be null). success only on the async branch."

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description's 'Read-only.' adds nothing. The 'Returns:' line duplicates the existing output schema. The only genuine behavioral signal is the mention of period comparisons, which is modest added context over structured fields.

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?

Purpose and scope are front-loaded in the first sentence, capabilities follow, and the read-only note is a four-word line. The trailing 'Returns:' block partly repeats the output schema and could be dropped, but overall there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations and an output schema present, the safety and return-shape burden is covered. What is missing is guidance for a tool with zero required parameters: no statement of default scope (all-time? last month?), and no mention of the optional 'clientEmail' scoping for accountants, which is a meaningful behavioral difference.

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

Parameters3/5

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

Schema description coverage is 67%, so the schema carries most of the weight and baseline 3 applies. The description echoes the groupBy and metric enum values and the date-range concept, but says nothing about 'categories' or 'clientEmail' (accountant-only scoping), nor about behavior when no date range is supplied.

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?

States a specific verb+resource ('summarize the user's recorded expenses') and enumerates the exact grouping dimensions and metrics, so an agent can tell it apart from get_income_summary and search_expenses. It does not explicitly differentiate itself from analytical siblings like get_pnl or get_deep_analytics, which leaves some overlap to inference.

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

Usage Guidelines3/5

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

Usage is implied by the capability list ('supports date ranges, period comparisons, and total, count, or average metrics'), so an agent can infer that this is the tool for spending roll-ups. However, there are no explicit when-to-use/when-not rules and no named alternative such as get_pnl or get_deep_analytics for profit or deeper analysis.

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.