Synci

List accounts

list_accounts

Read-onlyIdempotent

List the user's connected financial accounts (bank, investment, crypto). Each is a lean summary: name, institution, category, currency, a balance block, account health, and earliest_available_date. IMPORTANT: balances can lag transactions — check balance.as_of (the last time balances synced) and caveat stale figures. IMPORTANT: earliest_available_date is the start of the account's synced history — a query for a period before it returns nothing because the data was never synced, NOT because there was no activity, so never report a total for a window that starts before it without caveating the coverage. Investment/crypto accounts have an empty balance block: read total_balance for the broker-reported portfolio value and cash_balance for uninvested cash, and call list_holdings for the positions behind them. verbose:true returns the full record. Sensitive identifiers are omitted.

Input Schema

Name	Required	Description	Default
`verbose`	No	When true, return the full account record instead of the lean summary.
`account_category`	No	Optional. Restrict results to a single account category.

Output Schema

Name	Required	Description	Default
`accounts`	Yes	Lean account summaries; with verbose:true each item is the full account record instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / accounts / items / properties / balance / properties / currency

Added value: +{
+  "description": "Currency of these figures. A multi-currency account (currency XXX) holds one balance per currency; this is the one reported.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 10, 2026

addedOutput schema / properties / accounts / items / properties / total_balance

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

First observedJul 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only establish the read-only/idempotent profile, and the description adds substantial non-obvious behavior: balances lag transactions so balance.as_of must be checked, earliest_available_date marks the start of synced history and empty results are a coverage artifact rather than zero activity, and sensitive identifiers are omitted. These are exactly the caveats that would otherwise cause an agent to report misleading totals.

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

Conciseness4/5

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

Front-loaded with the core purpose and the field list, then the two IMPORTANT caveats. It is on the long side, but each sentence carries operational consequence (stale balances, coverage gaps, empty investment balance blocks) rather than filler.

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?

An output schema exists so return values need not be documented, yet the description still covers the traps an agent must know: stale balance handling, synced-history boundaries, and where investment value lives. Nothing needed to call or interpret this tool correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by enumerating what the 'lean summary' actually contains versus the 'full record' that verbose:true returns. That concretely clarifies the effect of the verbose flag rather than merely restating it.

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 ('List the user's connected financial accounts') and immediately scopes it by naming the account types and the lean-summary fields returned. It also distinguishes itself from the sibling list_holdings by redirecting there for positions, so an agent can pick between them without opening schemas.

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?

Gives clear routing guidance: call list_holdings for the positions behind investment accounts, read total_balance/cash_balance for broker value, and use verbose:true for the full record. It stops short of an explicit 'do not use this for X' exclusion, so it is strong context rather than a complete when/when-not statement.

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?