Skip to main content
Glama

Truo

Income and savings

income_and_savings
Read-only

Income sources (aggregated: salary, other regular income, interest earned), the savings rate per month, and "money moved" (transfers between the user's own accounts plus flows that could not be attributed to spending or income, however many accounts are connected). Savings rate = (income − spending) / income. IMPORTANT: the savings rate is always an ESTIMATE, for two separate reasons. Money moved to or from accounts Truo can't see, and any other flow Truo classifies as a transfer, is set aside as "money moved", not counted as saving or spending, however many accounts are connected; connecting those accounts lets Truo see where that money went. Truo also sorts transactions into income, spending and transfers itself, and that sorting carries its own error however many accounts are connected. Every answer states the date the data is current as at.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "income_and_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
newest-timeNoInclusive end of the period, ISO 8601 date or date-time (e.g. 2026-05-31). Defaults to the most recent data.
oldest-timeNoInclusive start of the period, ISO 8601 date or date-time (e.g. 2026-05-01). Defaults to 90 days before the end of the period, or the start of available data if there is less than that. Pass this explicitly to ask about the household's full history.

Output Schema

NameRequiredDescriptionDefault
noteNo
monthsNo
periodNo
moneyMovedNo
totalSavedNo
totalIncomeNo
dataCoverageNo
incomeSourcesNo
incomeCoverageNo
interestEarnedNo
connectionNoticesNo
incomeSourcesNoteNo
overallSavingsRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / connectionNotices
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "not": {}
      +        },
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      ]
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

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-only, closed-world tool, yet the description still adds meaningful behavior: the savings-rate formula, the two independent error sources (unseen accounts/transfers and Truo's own classification), and the fact that every answer is stamped with an 'as at' date. That is exactly the kind of caveat an agent needs to relay to a user. It does not describe result granularity or volume, so a 4 rather than a 5.

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?

Outputs are front-loaded, which is good, but the phrase 'however many accounts are connected' is repeated three times and the estimate caveat is restated twice. The savings-rate formula is useful; the redundancy is not. Trimming the duplication would cost no information.

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?

With an output schema present, the description needn't explain return values, and annotations cover safety. What remains is the interpretive context — what 'money moved' means, why the savings rate is an estimate, and the data-currency stamp — all of which is supplied. Only the relationship to sibling income/spending tools is left unaddressed.

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 time parameters are fully documented in the schema, including defaults and the explicit 'full history' behavior. The description adds nothing about period selection or the default 90-day window. Baseline 3 applies when the schema carries the parameter burden.

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 names the specific outputs: aggregated income sources (salary, other regular income, interest earned), the monthly savings rate, and 'money moved'. That is a clear verb-less but concrete resource statement an agent can match to a request. It does not explicitly contrast with income_and_expenditure or monthly_trend, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The agent must infer from the field list whether this or income_and_expenditure answers an income question. The only conditional content is about data accuracy, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources