Dayze — Life Context

Expense Summary

get_expenses

Read-only

Cashflow totals at Finance FX. Use period all for all-time requests, never year. Requires OAuth or scoped credentials. ($0.10; API key required)

Input Schema

Name	Required	Description	Default
`period`	No	all: no date filter; month: last 30 days (default); year: last 365 days.

Output Schema

Name	Required	Description
`net`	No
`usd`	No	Totals converted to USD (approximate FX).
`count`	No
`spend`	No
`income`	No
`period`	Yes
`partial`	No	True when the headline USD totals exclude unconverted currencies.
`currency`	No
`by_currency`	No
`period_days`	No	Window length in days; 0 means all time (no date filter).
`unconverted`	No
`multi_currency`	No
`top_categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 24, 2026

changedInput schema / properties / period / description

Previous value: -"Summary window. Default month."New value: +"all: no date filter; month: last 30 days (default); year: last 365 days."

changedInput schema / properties / period / enum

Previous value: -[
-  "month",
-  "year"
-]New value: +[
+  "month",
+  "year",
+  "all"
+]

changedOutput schema / properties / period / enum

Previous value: -[
-  "month",
-  "year"
-]New value: +[
+  "month",
+  "year",
+  "all"
+]

addedOutput schema / properties / period_days / description

Added value: +"Window length in days; 0 means all time (no date filter)."

Changed2 schema fields changedOct 16, 2026

addedOutput schema / properties / partial

Added value: +{
+  "description": "True when the headline USD totals exclude unconverted currencies.",
+  "type": "boolean"
+}

addedOutput schema / properties / unconverted

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "Native-currency amounts excluded from the converted totals.",
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / period

Added value: +{
+  "description": "Summary window. Default month.",
+  "enum": [
+    "month",
+    "year"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 2, 2026

addedOutput schema / properties / by_currency

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "Per-currency spend/income/net — never FX-converted.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / multi_currency
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / usd

Added value: +{
+  "additionalProperties": true,
+  "description": "Totals converted to USD (approximate FX).",
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "income": {
+      "type": "number"
+    },
+    "net": {
+      "type": "number"
+    },
+    "period": {
+      "enum": [
+        "month",
+        "year"
+      ],
+      "type": "string"
+    },
+    "period_days": {
+      "type": "number"
+    },
+    "spend": {
+      "type": "number"
+    },
+    "top_categories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "period"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish this is a safe read (readOnlyHint/ destructiveHint false), so the bar is lower, and the description adds real cost-and-access context: OAuth or scoped credentials, an API key, and a $0.10 charge. It stops short of describing aggregation behavior, currency handling, or grouping, and the overlapping "OAuth or scoped credentials" plus "API key required" wording is slightly muddled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core statement, but telegraphic fragments like "at Finance FX" and the parenthetical "($0.10; API key required)" are cryptic rather than compressing real content, and the key parameter rule is buried mid-string.

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?

An output schema exists, so return values need not be explained, and access/cost are covered. What is missing is the conceptual frame an agent needs to call this correctly — whether totals are net or expenses-only, what currency or period boundary applies — which the schema and annotations do not supply.

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 coverage is 100% and the enum already spells out month/all/year, so the baseline is 3. The description earns above baseline by adding a rule that resolves the truest ambiguity in the enum: for all-time requests use all, never year — guidance an agent could not derive from the schema, where year plausibly reads as 'all of this year'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Cashflow totals at Finance FX" signals an aggregation read, and the title adds "Expense Summary", but neither states precisely what is totaled (expenses only? income minus expenses?) or at what granularity. With many finance siblings (get_finance, get_transactions, get_money_between_people, search_transactions) the description never distinguishes this tool from them, leaving the agent to guess.

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?

The one explicit directive — "Use period all for all-time requests, never year" — is genuinely actionable and steers the most likely mistake. However, there is no guidance on when to reach for this tool instead of get_finance or get_transactions, so the choice among siblings remains implicit.

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

All Dayze — Life Context tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.