Skip to main content
Glama
BradMorphsters

tuskledger-mcp

list_accounts

List all connected accounts in Tusk Ledger with balances, types, and last sync timestamps. Use this to identify available accounts before analyzing transactions or holdings.

Instructions

List every connected account in Tusk Ledger with current balance, type (checking, savings, credit, investment, loan), and last-sync timestamp. Use this first to understand what accounts exist before drilling into transactions or holdings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The HTTP client method `list_accounts()` that performs the actual GET /api/accounts/ request to the backend.
    def list_accounts(self) -> list[dict]:
        return self._request("GET", "/api/accounts/")
  • Tool registration: defines the 'list_accounts' tool with name, description, and empty input schema.
    Tool(
        name="list_accounts",
        description=(
            "List every connected account in Tusk Ledger with current "
            "balance, type (checking, savings, credit, investment, loan), "
            "and last-sync timestamp. Use this first to understand what "
            "accounts exist before drilling into transactions or holdings."
        ),
        inputSchema={"type": "object", "properties": {}, "additionalProperties": False},
    ),
  • Dispatch handler: routes the 'list_accounts' tool call to `client.list_accounts()`.
    if name == "list_accounts":
        return client.list_accounts()
  • Test verifying the dispatch of 'list_accounts' calls the client method correctly.
    def test_dispatch_list_accounts_calls_client():
        client = MagicMock()
        client.list_accounts.return_value = [{"id": 1, "name": "Checking"}]
        out = srv._dispatch("list_accounts", {}, client)
        client.list_accounts.assert_called_once_with()
        assert out == [{"id": 1, "name": "Checking"}]
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists all accounts with selected fields and implies a read operation. However, it omits any mention of potential limitations (e.g., pagination, data freshness) or side effects. The description is adequate but not comprehensive.

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: the first clearly states output content, the second provides usage guidance. It is front-loaded and contains no unnecessary words, making it highly efficient.

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?

Given no parameters, no output schema, and no annotations, the description is fairly complete. It states what is returned and when to use it. It does not address error conditions or scale limits, but for a simple list tool this is sufficient.

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 input schema has no parameters and is 100% covered. The description adds no parameter-related meaning because there are none. Baseline for 0 parameters is 4, and the description appropriately focuses on output content.

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 uses specific verb+resource ('List every connected account') and enumerates returned fields (balance, type, timestamp). It distinguishes from sibling tools by advising to use this first before drilling into transactions or holdings, clearly differentiating its purpose.

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 explicitly states when to use the tool ('Use this first to understand what accounts exist') and contrasts with drilling into transactions or holdings. It could be improved by explicitly noting when not to use it, but the guidance is clear enough.

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