Skip to main content
Glama

Open the dashboard

open_dashboard
Read-onlyIdempotent

Open the dashboard card: the client's accounts, strategies and the catalogue, with tabs.

The one tool that draws the dashboard. The ``describe_*``, ``list_*`` and
``find_*`` reads return figures and rows without it.

``portfolio_id`` opens on that strategy or account; omitted, the card opens on
the list. ``tab`` opens on that tab ('returns', 'weights', 'risk', 'fundamentals',
'outlook' or 'construction': how a strategy is built); omitted, 'returns'
('weights' before a backtest).
``compare_id`` puts another strategy, account or market benchmark beside
``portfolio_id`` on every tab: use it whenever the client asks to compare, put
side by side, or measure one against another. Returns figures cover
``portfolio_id``'s history, and the comparison's are given only for periods
its own record fully covers.
``simulations`` are saved simulations from ``list_simulations`` or
``save_simulation``, selected in the card's comparison instead, so every tab
except returns shows ``portfolio_id`` beside itself with them applied. Each is on
``portfolio_id`` or an account under it, such as everything the client holds,
and an account takes at most one.

Returns a digest of the opened tab; with ``compare_id``, both sides' holdings,
risk, outlook and track records; with simulations, the tab measured with them
applied. On a strategy whose backtest ``get_backtest_status`` reports done, tab
'returns' shows the finished record.

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": "open_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNo
person_idNoThe id of one person, family or entity this login holds. Omit for everything this login holds.
compare_idNo
simulationsNo
portfolio_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / Tab / enum
      Previous value: -[
      -  "returns",
      -  "outlook",
      -  "weights",
      -  "risk",
      -  "fundamentals"
      -]New value: +[
      +  "returns",
      +  "outlook",
      +  "weights",
      +  "risk",
      +  "fundamentals",
      +  "construction"
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, yet the description adds substantial behavior: comparison figures are only returned for periods the comparison's own record fully covers; simulations apply to every tab except 'returns' and an account takes at most one; 'returns' shows the finished record only once get_backtest_status reports done; 'weights' is the default before a backtest. This is exactly the extra context annotations cannot express.

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?

Purpose and sibling differentiation are front-loaded in the first two sentences, and each subsequent paragraph maps to a parameter, so structure is sound. At roughly 280 words with some densely packed clauses (e.g. the simulations paragraph), it is longer than strictly necessary and could be trimmed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by explaining the returned digest, including how compare_id and simulations change the payload. What remains uncovered is person_id's scoping effect and any error/precondition behavior beyond the backtest-status note, both of which matter for a fully self-contained definition.

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 only 20%, so the description must carry the load, and it does for four of five parameters: portfolio_id ('opens on that strategy or account; omitted, the card opens on the list'), tab (enum values plus defaults and the 'construction' gloss), compare_id, and simulations (per-account numbering, at most one per account). The gap is person_id, which is never mentioned in the description and is only explained in the schema.

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 ('Open the dashboard card: the client's accounts, strategies and the catalogue, with tabs') and immediately differentiates: 'The one tool that draws the dashboard. The describe_*, list_* and find_* reads return figures and rows without it.' An agent can distinguish it from the ~40 siblings without opening a schema.

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 explicit selection rules: use compare_id 'whenever the client asks to compare, put side by side, or measure one against another', and derives simulations from list_simulations/save_simulation. It also names the alternative path (describe_*/list_*/find_* for raw figures) which functions as a when-not.

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.

Resources