Skip to main content
Glama
BradMorphsters

tuskledger-mcp

by BradMorphsters
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_net_worth

Calculate net worth (assets minus liabilities) with 12-month trend. Shows point-in-time snapshot from last sync; optionally retrieve full history.

Instructions

Current net worth (assets minus liabilities) plus a 12-month trend. Numbers are point-in-time from the last sync, not live-computed. Use list_stale_accounts to verify freshness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
historyNoIf true, return the full snapshot history instead of just latest.

Implementation Reference

  • tuskledger_mcp/server.py:172-186 (registration)
    Tool registration in the TOOLS list with name='get_net_worth', description, and inputSchema supporting an optional 'history' boolean parameter.
    Tool(
    name="get_net_worth",
    description=(
        "Current net worth (assets minus liabilities) plus a 12-month "
        "trend. Numbers are point-in-time from the last sync, not "
        "live-computed. Use list_stale_accounts to verify freshness."
    ),
    inputSchema={
        "type": "object",
        "properties": {
            "history": {"type": "boolean", "description": "If true, return the full snapshot history instead of just latest."},
        },
        "additionalProperties": False,
    },
),
  • tuskledger_mcp/server.py:296-297 (handler)
    Dispatch handler for 'get_net_worth' — calls client.net_worth_history() if the 'history' argument is truthy, otherwise calls client.net_worth_latest().
    if name == "get_net_worth":
    return client.net_worth_history() if a.get("history") else client.net_worth_latest()
  • tuskledger_mcp/client.py:151-156 (helper)
    Client helper methods: net_worth_latest() GETs /api/net-worth/latest and net_worth_history() GETs /api/net-worth/.
    # net worth
def net_worth_latest(self) -> dict | None:
    return self._request("GET", "/api/net-worth/latest")

def net_worth_history(self) -> list[dict]:
    return self._request("GET", "/api/net-worth/")
  • tuskledger_mcp/server.py:179-185 (schema)
    Input schema for get_net_worth: type 'object' with an optional 'history' boolean property and additionalProperties set to False.
    inputSchema={
    "type": "object",
    "properties": {
        "history": {"type": "boolean", "description": "If true, return the full snapshot history instead of just latest."},
    },
    "additionalProperties": False,
},

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Without annotations, the description adds value by disclosing that numbers are point-in-time from last sync, not live-computed. It does not mention rate limits or auth, but for a read-only tool, this is acceptable.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the main purpose, and every sentence adds value. No unnecessary words.

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?

For a low-complexity tool (one optional parameter, no output schema), the description explains the main output, data freshness, and a usage hint. It is mostly complete, though return format details are omitted.

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?

The input schema fully describes the single parameter 'history' with a description. The tool description does not add additional meaning beyond that, so baseline 3 is appropriate.

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 clearly states the tool returns 'current net worth (assets minus liabilities) plus a 12-month trend', specifying the resource (net worth) and action (get). It distinguishes from siblings by noting data is point-in-time from last sync, not live-computed.

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 description tells when to use the tool to get net worth with trend and advises using list_stale_accounts to verify data freshness. It does not explicitly mention when not to use, but the sibling list provides context for alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BradMorphsters/tuskledger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server