Skip to main content
Glama

The user's saved custom views, or one view with its rows

get_views
Read-onlyIdempotent

Without viewId: lists the user's saved custom views (id, name, source, chart type, columns, who made it, whether it is on the dashboard). With viewId: that view's full spec plus its result, computed by the app from the user's real data: columns, rows (up to 200), totals and KPIs. Use the spec when editing a view with manage_view. Views belong to the user, not to one portfolio; profile picks whose numbers a run shows. range applies with viewId only.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoThe period to run it over, for views whose source has one and whose spec follows the dashboard: 1m (default), 3m, ytd, 1y or all. A spec that fixes its own range keeps it.
viewIdNoOptional; omit to list every view: 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
viewNoWith viewId: the view, plus its full `spec`.
as_ofNoWhen it was computed, epoch ms.
countNoHow many views the user has.
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.
rangeNoThe period it was run over.
viewsNoWithout viewId: the user's views, most recently edited first.
resultNoWith viewId: what it shows now.
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).
view_urlNoThe view in the app.
next_stepNoWhat the user should do about data_status.
source_urlNoLink to the page in the WhereItGoes app that shows this data.
views_noteNo
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. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's job is to add operational context, which it does: results are 'computed by the app from the user's real data', rows are capped at 'up to 200', totals and KPIs are included, and views belong to the user rather than a portfolio. The 200-row cap is exactly the kind of disclosure annotations cannot convey. It stops short of describing pagination or what happens past the row limit.

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 two-mode framing is front-loaded and the parallel 'Without viewId / With viewId' construction is easy to scan. It is dense and slightly overpacked with backtick-quoted parameter names in the final sentences, but no sentence is 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?

An output schema exists, so return values needn't be re-explained, and with three optional parameters fully documented in the schema, the description supplies everything else: mode switching, the row limit, data provenance, portfolio scoping, and the range/viewId dependency. Nothing an agent needs in order to call this 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 would be 3; the description earns more by clarifying the interaction between parameters that the schema does not state, namely that `range` only takes effect when `viewId` is supplied and that `profile` chooses whose numbers a run reflects. This resolves ambiguity an agent reading the schema alone would hit.

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 specific verb and resource and splits the tool into its two modes explicitly: 'Without viewId: lists the user's saved custom views' versus 'With viewId: that view's full spec plus its result'. It even enumerates the returned fields for each mode, so an agent can distinguish this from preview_view, list_view_sources or manage_view without opening any 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?

It gives concrete routing guidance ('Use the spec when editing a view with manage_view') and a hard usage rule ('`range` applies with viewId only'). What it lacks is an explicit statement of when to use this instead of preview_view or list_view_sources, so the agent must infer that from the sibling names alone.

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.