Skip to main content
Glama

Place a saved custom view on the user's dashboard (applies immediately)

add_view_to_dashboard
Idempotent

Adds one of the user's saved views to the dashboard of a portfolio, at the end, as a widget. Applies immediately, and is safe to repeat: a view already there answers already and nothing changes. A dashboard holds at most 24 widgets; a full one answers full and nothing is added, so tell the user to remove one in the app. size is "full" (default, the whole row) or "half". Each portfolio has its own dashboard, picked by profile. Needs the connection's "make changes" permission (write_not_permitted otherwise).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "viewId": "<viewId>"
    },
    "name": "add_view_to_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo"full" (default) spans the row; "half" sits beside another half-width widget.
viewIdYesThe view to place: the `id` of a saved view, exactly as get_views returns it.
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
viewNoThe view acted on (with its spec after a create or update).
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, rate_limited, limit_reached, view_unavailable. No data fields come with it; read `message` to the user rather than retrying the same call.
statusNoWhat happened, and it already happened: created / updated / deleted for manage_view; added / already / full for add_view_to_dashboard (already and full changed nothing).
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).
previousNoAfter an update: what it was.
view_urlNo
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.
removed_from_dashboardsNoAfter a delete: how many dashboards it was taken off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it names the idempotent outcome (`already`), the capacity failure (`full`) with recovery advice, the permission requirement and its error code (write_not_permitted), and that the effect is immediate. Annotations only flag idempotentHint and destructiveHint=false; the description supplies the concrete failure modes those hints 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-loaded with the action and placement, then failure modes and permission in descending priority; nearly every clause carries information (default size, cap, error codes). It is dense rather than padded, though the run-on middle sentences could be split for 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?

For a 3-parameter mutation with an output schema, the definition covers everything an agent needs: what changes, immediate effect, repeat safety, capacity limit, permission gate, and per-portfolio scoping. Return-value details are rightly left to the output schema, while the important status codes are still surfaced.

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 baseline is 3, but the description adds real meaning: `size` defaults to full-width, and `profile` selects which portfolio's dashboard is written to because each portfolio has its own. That dashboard-selection semantics is a useful clarification beyond the schema text.

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?

Opens with a specific verb, resource and placement ('Adds one of the user's saved views to the dashboard of a portfolio, at the end, as a widget'), which is precise enough to distinguish it from get_views and preview_view without opening either schema.

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?

Clear operating context: it applies immediately, is safe to repeat, and hits a hard cap of 24 widgets where the agent should tell the user to remove one in the app. It stops short of explicitly naming an alternative tool to call first (e.g. get_views for the viewId), so it is strong but not a full when/when-not/alternatives statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.