Dayze — Life Context

Save Net Worth Entry

save_net_worth_entry

Add or update today's value of a manual net worth entry (a bank account, a property). source starts with manual. (manual.bank.dbs); asset_class equities, crypto, cash, real_estate, business, collectibles, debt or other; value_usd. Broker and wallet sources can't be written here. ($0.10; API key required)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "asset_class": "<asset_class>",
      "value_usd": "<value_usd>"
    },
    "name": "save_net_worth_entry"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	manual.bank.dbs
`currency`	No	ISO 4217 currency code, e.g. USD.
`value_usd`	Yes	Current value in US dollars, e.g. 8500.
`request_id`	No	Client idempotency key (retries return original result).
`asset_class`	Yes	Net worth asset class, e.g. cash.
`source_label`	No	Display label for the net worth entry, e.g. DBS Savings.
`idempotency_key`	No	Alias for request_id.

Output Schema

Name	Required	Description
`entry`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026
- addedInput schema / properties / asset_class / description
```
Added value: +"Net worth asset class, e.g. cash."
```
- addedInput schema / properties / currency / description
```
Added value: +"ISO 4217 currency code, e.g. USD."
```
- addedInput schema / properties / source_label / description
```
Added value: +"Display label for the net worth entry, e.g. DBS Savings."
```
- addedInput schema / properties / value_usd / description
```
Added value: +"Current value in US dollars, e.g. 8500."
```
AddedNov 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the write/safe profile is known. The description adds meaningful context beyond that: it is an upsert scoped to "today's value", it is restricted to manual sources, it costs $0.10, and it requires an API key. It does not explain what happens to previously recorded values or whether the upsert overwrites history, which is the main remaining gap for a mutation tool.

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 purpose is front-loaded, but the middle section degenerates into a semicolon-separated fragment ("(manual.bank.dbs); asset_class equities, crypto, cash...") that largely duplicates the enum already present in the schema. The parenthetical pricing/auth note at the end is dense but useful; trimming the enum recitation would make the whole definition tighter.

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?

An output schema exists, so return values need not be explained, and the description covers auth, cost, upsert semantics, source restriction, and the required fields. The one thing an agent might still want is whether a currency other than USD causes conversion rather than rejection, which is left to the schema's brief currency description.

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 coverage is 100%, so the baseline is 3. The description does add one genuinely new constraint not encoded in the schema: the source value must begin with "manual". However, it also spends words restating the asset_class enum and the value_usd meaning, which the schema already documents verbatim.

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 a specific verb pair ("Add or update") and resource ("today's value of a manual net worth entry") and clarifies the resource with concrete examples (a bank account, a property). It does not name any sibling tool, so the agent must infer how this differs from get_net_worth or log_entry, which keeps it below 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The exclusion "Broker and wallet sources can't be written here" gives an explicit when-not condition, and "source starts with manual" gives a precondition for use. No alternative tool is named for the excluded cases, so the agent is told what not to do but not where to go instead.

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

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.