Skip to main content
Glama

ExpenseBot

by io.github.TotesMagotes
OverviewDiscussionsAdmin

get_deep_analytics

Read-only

Run deeper, multi-step analytics on the user's expenses. Use for explanatory questions like 'why did my spending increase' or 'compare Q1 vs Q2'. Takes 10-30 seconds (runs as a background job, polled automatically). Returns: { message, data: { ..., sampleMeta? } } where sampleMeta.isTruncated indicates whether the agent saw the full dataset.

Input Schema

NameRequiredDescriptionDefault
queryYesThe analytics question to answer
dateRangeNoTime period filter; use exactly one variant matching the user's phrasing.

Output Schema

NameRequiredDescriptionDefault
dataNoInline branch: computed analytics, or null when no spreadsheet / no data.
typeNoAsync branch only: "analytics_pending" — poll pollEndpoint or call poll_analytics with jobId.
jobIdNoAsync branch only.
messageNoHuman-readable narrative (both branches).
successNoAsync branch only.
responseNoChat alias of message.
pollEndpointNoAsync branch only.
pollIntervalNoAsync branch only: milliseconds.
estimatedTimeNoAsync branch only: seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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."
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only, non-destructive annotations, the description discloses important behavior: it takes 10-30 seconds, runs as a background job that is polled automatically, and returns a truncation flag indicating whether the full dataset was visible. These details materially affect how an agent should invoke and interpret the tool.

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 compact and front-loaded: purpose first, then usage examples, then latency/async behavior, then return-shape caveat. Every sentence provides useful information without repetition.

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?

Given the annotations, full schema coverage, and existing output schema, the description is complete enough to call the tool correctly. It adds the important async latency and truncation semantics that an agent needs when interpreting results.

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 100%, so both the query and dateRange parameters are already well documented in the schema. The description reinforces usage with examples like Q1 vs Q2, but it does not add parameter-level meaning beyond what the schema provides.

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 ('Run deeper, multi-step analytics on the user's expenses') and distinguishes the tool from simpler summary or lookup siblings through the phrase 'deeper, multi-step'. The explanatory-question examples further clarify its distinct analytical role.

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 clear when-to-use guidance with concrete examples such as 'why did my spending increase' and 'compare Q1 vs Q2'. It does not explicitly name alternatives like get_spending_summary or get_pnl, so the agent must infer that simpler summaries belong elsewhere.

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

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

Resources