WhereItGoes

Lifetime trade totals per asset and daily activity calendar

get_trading_activity

Read-onlyIdempotent

Read trading activity over the whole history (no window), in one of two views. asset_totals: for every asset traded, one row per asset and quote currency with quantity bought and sold, amount spent and received in that quote, trade count and first and last trade time, largest buy volume first; these are raw sums, not profit, and there is no asset filter, so pick the row you need. calendar: per UTC day with any activity, counts of trades, deposits, withdrawals and income events, trade volume in USD and realized and unrealized P&L, oldest first, plus all-time totals and the active years; past 200 active days the most recent 200 are kept and truncated says so, while totals always cover everything. Use for "how much ETH have I bought in total", "my busiest days". For realized profit per pair use get_performance; for the individual trades use get_movements with kind TRADE.

Input Schema

Name	Required	Description	Default
`view`	Yes	Which view to read: asset_totals (lifetime buy and sell sums per asset); calendar (per-day activity counts and P&L). 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).
`calendar`	No	Present when view = "calendar".
`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.
`upgrade_url`	No	Where the user can upgrade, on an upgrade_required refusal.
`asset_totals`	No	Present when view = "asset_totals".
`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 readOnly/idempotent annotations it discloses behavior that materially affects interpretation: values are raw sums not profit, there is no asset filter so the caller must pick the row, calendar is capped at the 200 most recent active days with a `truncated` flag while `totals` always cover everything. Those are exactly the traps an agent would otherwise fall into.

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 scope constraint and the two views are front-loaded and every clause carries information. The view paragraphs are dense run-on sentences, which costs readability even though little is redundant.

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, yet the description still supplies the interpretive context that matters (raw sums, ordering, truncation) so the agent knows how to read results. Nothing needed to call 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 further by spelling out what each view value actually yields (columns, sort order, truncation semantics) rather than just restating the enum. It adds nothing for the `profile` parameter, which is left entirely to the schema, keeping it just short of a 5.

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 (read trading activity) with an explicit scope (whole history, no window) and enumerates the two views and their row shapes. An agent can immediately tell this apart from get_performance and get_movements.

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 concrete example questions ("how much ETH have I bought in total", "my busiest days") plus explicit routing: get_performance for realized profit per pair, get_movements with kind TRADE for individual trades. Both the when and the when-not are covered.

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.