Skip to main content
Glama
Sign In

WhereItGoes

by money.whereitgoes
OverviewDiscussionsAdmin

Target allocation plan

get_target_allocation
Read-onlyIdempotent

Read the user's target allocation: the plan they MEANT to hold, as set.rows of {subject, targetPct, bandPct} largest first, or set: null if they never set one. set.dim names the axis: "asset" means each subject is a ticker (BTC), "sector" means each is one of our sector names (Layer 1, DeFi, Stablecoins). bandPct is the tolerance in percentage POINTS, so a 40% target with a 5-point band is on plan anywhere from 35% to 45%. Use for "what is my target allocation", "what was my plan", and before set_target_allocation so an edit starts from the real plan. This is the INTENTION only: for what they actually hold against it, read the drift in get_portfolio (overview), which scores the two together.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_target_allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoWhich 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

NameRequiredDescriptionDefault
setNonull when no target allocation is set.
errorNoPresent 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.
messageNoPlain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user.
profileNoThe portfolio these figures belong to (absent on list_profiles).
next_stepNoWhat the user should do about data_status.
source_urlNoLink to the page in the WhereItGoes app that shows this data.
data_statusNoPresent 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_urlNoWhere the user can upgrade, on an upgrade_required refusal.
stock_assetsNoPresent when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "description": "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.",
+      "type": "string"
+    },
+    "message": {
+      "description": "Plain-language explanation that accompanies `error` or a proposed change.",
+      "type": "string"
+    },
+    "profile": {
+      "additionalProperties": true,
+      "description": "The portfolio these figures belong to (absent on list_profiles).",
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    "set": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "dim": {
+              "description": "Axis of the plan: \"asset\" (subjects are tickers), \"sector\" (subjects are sector names) or \"class\".",
+              "type": "string"
+            },
+            "rows": {
+              "description": "Largest target first.",
+              "items": {
+                "additionalProperties": true,
+                "properties": {
+                  "bandPct": {
+                    "description": "Tolerance in percentage POINTS either side.",
+                    "type": "number"
+                  },
+                  "subject": {
+                    "type": "string"
+                  },
+                  "targetPct": {
+                    "description": "Target share, percent.",
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "subject",
+                  "targetPct",
+                  "bandPct"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "updatedAt": {
+              "description": "Epoch ms.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "dim",
+            "rows",
+            "updatedAt"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "null when no target allocation is set."
+    },
+    "source_url": {
+      "description": "Link to the page in the WhereItGoes app that shows this data.",
+      "type": "string"
+    },
+    "stock_assets": {
+      "additionalProperties": true,
+      "description": "Present when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto.",
+      "properties": {
+        "assets": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "asset": {
+                "type": "string"
+              },
+              "ticker": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "asset",
+              "ticker"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "note": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "note",
+        "assets"
+      ],
+      "type": "object"
+    },
+    "upgrade_url": {
+      "description": "Where the user can upgrade, on an upgrade_required refusal.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / profile / description
      Previous value: -"Which portfolio to read, by name or id, for accounts that have more than one. Omit to use this connection's default. Call list_profiles first if the user names a portfolio you have not seen."New value: +"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."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, yet the description adds materially: the null-result case when no plan exists, the rows/dim structure, and the key semantic warning that this is intention only. That last point prevents a plausible misuse (treating targets as holdings), which annotations cannot convey.

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-loads the core definition, then the return shape, then usage. The band example is long but earns its place by clarifying 'percentage points' ambiguity. Slightly dense, but nearly every clause carries operational meaning.

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 needn't enumerate returns, yet explaining set.rows/set.dim/bandPct semantics and the null state is genuinely useful for interpretation. Combined with the intention-vs-actual distinction, an agent has everything needed to call and correctly use this tool.

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?

There is one optional 'profile' parameter with 100% schema description coverage, including default behavior and error cases. The description adds no parameter guidance beyond the schema, so the baseline of 3 is appropriate despite the overall richness.

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 ('Read the user's target allocation') and immediately defines what the resource is: intended plan vs actual holdings. It explicitly contrasts with get_portfolio's drift and set_target_allocation, so an agent can distinguish it from every sibling without reading schemas.

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 concrete trigger phrases ('what is my target allocation', 'what was my plan') and explicitly says to call it before set_target_allocation so edits start from the real plan. It also names the alternative for actual-vs-target comparison (drift in get_portfolio).

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

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