Skip to main content
Glama

get_family_overview

Read-only

Retrieve the family's current financial overview—income, expenses, savings, loans, goals, and data gaps—before advising.

Instructions

The family as it is now, in the family currency: the 3-month average income and expenses, savings, what is left for living, the loan payment share, the emergency fund, the loans, the goals and their plan (the financial-independence goal's projected month includes an assumed 8% return a year on what it holds), each member's income share, the income sources by category (incomeSources: a month's average per category, with its flow and the one-off flag) and the income a month left unallocated, the health metrics and the data gaps. Call it before advising; every amount is computed by the server. Follow answerRules in your answer.

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": "get_family_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses meaningful behavior: 'every amount is computed by the server' (the agent need not do arithmetic), the currency framing, and a specific modelling assumption that the FI goal's projection embeds an 8% annual return. It also imposes an output protocol ('Follow answerRules'), which is genuinely useful behavioral context. Absent pagination or freshness caveats, but those are minor for a zero-parameter read.

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?

The lead clause is reasonably front-loaded, and because there is no output schema the enumerated return fields do earn their place. However, the entire payload is one sprawling run-on sentence with nested parentheticals, making it hard to scan and easy for an agent to lose the operative instruction buried at the end.

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 no output schema, the description carries the full burden of describing returns and does so thoroughly: aggregates, loan share, emergency fund, goals plus projection assumption, per-member income share, categorized income sources and unallocated income, health metrics, and data gaps. The reference to 'answerRules' is not defined locally and nesting/structure of the response is left implicit, but nothing blocks a correct call.

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?

The tool takes no parameters, so the baseline is 4; there is nothing for the description to explain. Its parenthetical notes on incomeSources ('a month's average per category, with its flow and the one-off flag') describe returned fields rather than inputs, and are credited under completeness instead.

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 opens by naming the resource ('The family as it is now, in the family currency') and then enumerates the exact contents, so an agent knows this is a whole-household financial snapshot rather than a single-object read. It never contrasts itself with siblings like get_month_draft or get_advisor_guide, so differentiation is inferred from content alone.

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?

'Call it before advising' gives an explicit trigger condition and ordering relative to advisory work, which is the key usage cue. There are no exclusions or named alternatives distinguishing it from get_advisor_guide or get_month_draft, so it stops short of full routing guidance.

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