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.

Input Schema

TableJSON 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

TableJSON 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.9/5.0

Behavior5/5

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

Annotations already mark the call as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: balance snapshots may lag transactions, negative CLOSING_BOOKED on credit accounts means amount owed, and investment/crypto accounts typically lack snapshots. This is exactly the kind of context annotations cannot express.

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 dense sentences, front-loaded with the core action, followed by caveats and alternatives. No filler or repetition of schema content.

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?

The output schema exists, so return-value documentation is not the description's job. It covers staleness, credit semantics, and the investment/crypto exception, making it complete for a one-parameter read-only tool.

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 fully documents account_id at 100% coverage, so the baseline is 3. The description adds meaning by clarifying that exactly one account is targeted and by describing account-type-dependent balance semantics, which goes beyond the schema's 'id of the financial account' definition.

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 and resource: 'Get balance snapshots for one account', and lists concrete snapshot types. It also distinguishes itself from sibling tools by explicitly steering investment/crypto account cases to list_holdings and balance fields.

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?

Provides clear context for when the tool is appropriate versus alternatives, especially for investment/crypto accounts where snapshots usually don't exist. The credit-account interpretation guidance and stale-data caveat further tell the agent how to use the result correctly.

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?