Synci

Get account balance

get_account_balance

Read-onlyIdempotent

Get balance snapshots for one account (e.g. INTERIM_AVAILABLE, EXPECTED, CLOSING_BOOKED). as_of is when balances last synced — they can lag transactions, so caveat stale figures. For a credit account a negative CLOSING_BOOKED is the amount owed (not overdrawn). Investment/crypto accounts usually have no balance snapshots: read total_balance for the broker-reported portfolio value and cash_balance for uninvested cash, and call list_holdings for the positions behind them.

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": {
      "account_id": "<account_id>"
    },
    "name": "get_account_balance"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes	The id of the financial account to fetch balances for, as returned by list_accounts.

Output Schema

Name	Required	Description
`note`	No	Present when the account has no snapshots; points at list_holdings for investment/crypto value.
`as_of`	No	When balances last synced (ISO 8601); balances can lag transactions.
`balances`	Yes	Newest first, at most 20 snapshots. Empty for accounts without balance snapshots.
`account_id`	Yes
`cash_balance`	No
`total_balance`	No	Broker-reported total account value (positions plus cash); investment accounts only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedOutput schema / properties / total_balance

Added value: +{
+  "description": "Broker-reported total account value (positions plus cash); investment accounts only.",
+  "properties": {
+    "amount": {
+      "type": [
+        "string",
+        "number"
+      ]
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds non-obvious semantics beyond them: `as_of` is a sync time that can lag transactions, and a negative CLOSING_BOOKED on a credit account means amount owed rather than overdrawn. It does not cover auth, pagination, or rate limits, keeping it just below a 5.

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?

Three tight sentences, no filler; the snapshot scope leads, the staleness caveat follows, and the investment-account redirect closes. Every sentence carries distinct, actionable information.

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?

Given an output schema exists, the description is not obligated to explain return fields, yet it does so only where agent behavior changes (staleness caveat, negative credit balance, accounts with no snapshots). Nothing needed to invoke or interpret the tool correctly is missing.

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% with a single, well-documented `account_id`, so the schema already does the work and the baseline is 3. The description's added value is about returned snapshot fields rather than parameter syntax, so it adds nothing parameter-level beyond the schema.

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?

States a specific verb (get) and resource (balance snapshots) scoped to one account, and enumerates the snapshot types (INTERIM_AVAILABLE, EXPECTED, CLOSING_BOOKED). It also positions itself against the sibling list_holdings for the positions case, so an agent can select it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not: investment/crypto accounts usually have no snapshots, and the agent is routed to total_balance, cash_balance, and list_holdings instead. That is exactly the alternative-routing guidance the dimension asks for.

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

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