WhereItGoes

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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

TableJSON Schema

Name	Required	Description
`set`	No	null when no target allocation is set.
`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` or a proposed change.
`profile`	No	The portfolio these figures belong to (absent on list_profiles).
`source_url`	No	Link to the page in the WhereItGoes app that shows this data.
`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.

Changed1 schema field changedOct 23, 2026

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"
+}

Changed1 schema field changedOct 23, 2026

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."

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare the safe read-only, idempotent profile, but the description adds important behavior beyond them: it defines the returned `set.rows` shape, explains that `set: null` means no plan was ever set, and clarifies that bandPct is expressed in percentage points rather than percent. Those details materially affect how an agent interprets the result.

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?

The description is front-loaded with the core definition, then layers output shape, dimension semantics, band semantics, and usage routing in a compact sequence. Despite its length, every sentence adds operational meaning and there is no 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?

Although an output schema exists, the description preemptively explains the semantically important return values (`set.rows`, `set: null`, `set.dim`, and `bandPct`) that an agent would otherwise have to infer. Combined with its read-only annotations and complete parameter schema, nothing needed to call or interpret this tool is missing.

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 only one parameter, `profile`, and its schema description is already complete, covering name, id, default behavior, and error cases. The tool description adds no further guidance about the parameter itself, so the baseline of 3 is appropriate given full schema coverage.

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?

The description states a precise verb and resource: reading the user's target allocation, defined as the intended plan rather than actual holdings. It explicitly distinguishes this from get_portfolio drift and from set_target_allocation, so an agent can select it without opening sibling 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?

It names concrete triggering questions such as "what is my target allocation" and "what was my plan", and says to call it before set_target_allocation so edits start from the real plan. It also routes actual-holdings comparison to get_portfolio, giving both when-to-use and an explicit alternative.

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.