WhereItGoes

Connected exchanges, tracked wallets and sync status

get_connections

Read-onlyIdempotent

List where the portfolio's data comes from, in one of three views. exchanges: every exchange and data source the app supports, with configured true on the ones the user connected (count only those) and a masked key hint, never the key. wallets: the watch-only on-chain addresses tracked, with label, wallet family, chains scanned and whether enabled, plus the EVM chains this app can read (balanceOnly where history is unavailable). sync_status: whether a sync of this portfolio is running or queued right now, and its queue position. No view takes a window. They hold no balances (get_portfolio holdings carry a per-venue split), do not test live connectivity, and cannot start a sync, which runs automatically and from the WhereItGoes app; for when the last sync finished use get_portfolio (recent_change, lastSyncAt). Use for "which exchanges am I connected to", "is my Base address tracked", "is it still syncing". When nothing is connected yet, the answer says so (data_status "nothing_connected") with the app links to add a wallet address or an exchange API key; pass those to the user.

Input Schema

Name	Required	Description	Default
`view`	Yes	Which view to read: exchanges (supported and connected exchanges); wallets (tracked on-chain addresses); sync_status (is a sync running or queued now). Each view takes only the arguments the description lists for it.
`profile`	No	Which portfolio to read, for accounts with more than one: its id, or its name (exact, case-insensitive, e.g. "Trading"). Omit to read this connection's default portfolio; every answer names the portfolio it read in `profile`. An unknown or shared name returns profile_not_found or profile_ambiguous listing the real ones, and list_profiles shows them up front.

Output Schema

Name	Required	Description
`view`	No	Which view answered; its data is under the key of the same name.
`error`	No	Present ONLY when the call was refused instead of answered: upgrade_required (Pro plan needed), not_found, profile_not_found, profile_ambiguous, invalid_arguments, write_not_permitted. No data fields come with it; read `message` to the user rather than retrying the same call.
`message`	No	Plain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user.
`profile`	No	The portfolio these figures belong to (absent on list_profiles).
`wallets`	No	Present when view = "wallets".
`exchanges`	No	Present when view = "exchanges".
`next_step`	No	What the user should do about data_status.
`source_url`	No	Link to the page in the WhereItGoes app that shows this data.
`data_status`	No	Present only when the portfolio has no data yet. nothing_connected: no exchange and no wallet is connected, so empty lists and zeros mean "no data", NOT a $0 portfolio, and no data fields come with it (except on get_connections, get_alerts, get_target_allocation and list_profiles, which also answer). Send the user to next_step. syncing: a source is connected but its first sync is still running, so figures are partial and not final.
`sync_status`	No	Present when view = "sync_status".
`upgrade_url`	No	Where the user can upgrade, on an upgrade_required refusal.
`stock_assets`	No	Present when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedOutput schema / properties / data_status

Added value: +{
+  "description": "Present only when the portfolio has no data yet. nothing_connected: no exchange and no wallet is connected, so empty lists and zeros mean \"no data\", NOT a $0 portfolio, and no data fields come with it (except on get_connections, get_alerts, get_target_allocation and list_profiles, which also answer). Send the user to next_step. syncing: a source is connected but its first sync is still running, so figures are partial and not final.",
+  "enum": [
+    "nothing_connected",
+    "syncing"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / message / description

Previous value: -"Plain-language explanation that accompanies `error` or a proposed change."New value: +"Plain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user."

addedOutput schema / properties / next_step

Added value: +{
+  "additionalProperties": true,
+  "description": "What the user should do about data_status.",
+  "properties": {
+    "action": {
+      "enum": [
+        "connect_a_source",
+        "wait_for_first_sync"
+      ],
+      "type": "string"
+    },
+    "add_exchange_url": {
+      "description": "App page to connect an exchange with a read-only API key.",
+      "type": "string"
+    },
+    "add_wallet_url": {
+      "description": "App page to add a wallet address to watch.",
+      "type": "string"
+    },
+    "settings_url": {
+      "type": "string"
+    },
+    "sync_status_url": {
+      "description": "App page showing sync progress.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "action"
+  ],
+  "type": "object"
+}

AddedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only annotations, it discloses that keys are masked and never returned, that no balances are held, that sync cannot be started and runs automatically, and that empty connection states return data_status 'nothing_connected' with app links. These are substantive behavioral traits an agent could not infer from the annotations alone.

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?

The opening sentence front-loads the core purpose, and the rest is dense, view-by-view detail rather than padding. It is long but most sentences carry operational value; a tighter grouping of the view definitions could improve scanability.

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?

With an output schema present, return formatting need not be explained, and the description still covers all three views, constraints, the empty state, and alternatives. Nothing an agent needs in order to choose a view 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 adds real meaning per view: what exchanges/wallets/sync_status contain, that configured is counted only when true, and that no view takes a window. The profile parameter is left to the schema, which documents it fully.

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?

It states a specific verb and resource ('List where the portfolio's data comes from') and immediately enumerates the three views, making the scope unambiguous. It is clearly distinguishable from data-bearing siblings like get_portfolio and get_trading_activity.

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?

It gives explicit user-intent examples ('which exchanges am I connected to', 'is my Base address tracked', 'is it still syncing') and routes the agent elsewhere for last-sync timing via get_portfolio. It also states what the tool cannot do (start a sync, test connectivity), closing off wrong-use paths.

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

All WhereItGoes 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.