savi-tools

Expense summary

get_expense_summary

Read-only

Total expenses for a year with by-category and by-month breakdowns. Answers "what did I spend on software this year?" or "where is my money going?"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No	Calendar year. Defaults to the current year.
`category`	No	Optional category name to filter to (e.g. "Software & Subscriptions").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`basis`	No
`count`	Yes
`total`	Yes
`period`	Yes
`byMonth`	Yes
`byCategory`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 20, 2026

addedOutput schema / properties / basis

Added value: +{
+  "properties": {
+    "accountingMethod": {
+      "type": "string"
+    },
+    "definitions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "timezone",
+    "definitions"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "byCategory": {
+      "items": {
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "category": {
+            "type": "string"
+          },
+          "percentage": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "category",
+          "amount",
+          "percentage"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "byMonth": {
+      "items": {
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "month": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "month",
+          "amount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    },
+    "period": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "period",
+    "total",
+    "count",
+    "byCategory",
+    "byMonth"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the annual scope and breakdown behavior, which is useful but not extensive; it does not mention aggregation details, currency, or handling of uncategorized expenses.

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 two sentences with no redundancy. The first sentence states the core function, and the second provides illustrative examples, making it efficient and well-structured.

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 strong annotations, full schema coverage, and presence of an output schema, the description is complete enough for an agent to understand the tool's purpose and invoke it correctly. No critical gaps remain.

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 parameters (year and category) are already documented in the input schema. The description reinforces the category concept via the example question but adds no new parameter-level detail 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 clearly states the tool totals expenses for a year with by-category and by-month breakdowns, using a specific verb and resource. It also distinguishes itself from sibling tools like list_recent_expenses and get_cost_summary by emphasizing annual aggregation and breakdown dimensions.

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?

The description provides clear usage context through example questions ('what did I spend on software this year?') and implies the tool is for annual expense summaries. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to select it appropriately.

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

All savi-tools 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.

Resources

Need Help?