Truo

Weekly brief

weekly_brief

Read-only

A weekly brief of facts from the household's own records. It covers the 7 days ending on the newest date the data holds, beside the 7 days before them: money in, spending by category, money moved (transfers between the household's own accounts, cash withdrawals, and flows Truo could not attribute to spending or income), the recurring payments Truo began or stopped seeing that week, and payments on loan accounts with their dates. Use it when the household asks for their week, a weekly brief or what changed. Say each line as a fact. Leave out any suggestion of what to do next. A follow-up question asking for more facts from their own records is not one.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`asOf`	No
`note`	No
`week`	No
`loans`	No
`moneyIn`	No
`spending`	No
`weekNote`	No
`moneyMoved`	No
`weekBefore`	No
`weekBeforeNote`	No
`entriesThisWeek`	No
`recurringStarted`	No
`recurringStopped`	No
`spendingByCategory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / entriesThisWeek

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnlyHint and non-destructive annotations, the description specifies that lines should be stated as facts and that suggestions for next steps should be omitted. It also discloses exactly which record categories are included and that the window ends on the newest available date, though it does not discuss ordering or completeness edge cases.

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

Conciseness4/5

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

The description is front-loaded with purpose, time window, and content coverage, and most clauses earn their place. The final exclusion about follow-up questions is useful but somewhat awkwardly phrased and could be clearer.

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?

For a no-parameter, read-only tool with an output schema, the description supplies enough detail about scope, triggers, included data, and presentation style. Nothing essential for correct invocation appears to be missing.

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 has zero parameters, so there is no parameter meaning to add beyond what the schema provides. The baseline for a zero-parameter tool is 4.

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 resource and scope: a weekly brief of facts from the household's own records, covering two consecutive 7-day windows. It also enumerates the included content areas, so the agent can distinguish it from siblings like monthly_trend or spending_by_category.

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 explicit triggers such as when the household asks for their week, a weekly brief, or what changed, and it excludes follow-up questions asking for more facts. It does not route to named alternatives for adjacent requests like monthly summaries, so it stops short of full when/when-not guidance.

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

All Truo 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?