Skip to main content
Glama

Custom view vocabulary: sources, fields, formats and chart types

list_view_sources
Read-onlyIdempotent

The schema for custom views: every data source a view can read, each source's fields (dimensions and measures, with what they mean), the column formats, the render types (table, bar, pie, line, kpi), the ranges and the caps, plus the exact spec shape and its rules. Call this BEFORE writing a spec for preview_view or manage_view; a spec can only name what this lists, and anything else is refused with the path of the problem. available_sources is what THIS account can use. Takes no arguments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
capsNoLimits: columns, filters, sort keys, name length, spec size.
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.
guideNoThe full vocabulary and rules, written for a model: the spec shape, every source and field, and an example.
rangesNoRange values a spec may name.
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).
versionNoThe spec version, the `v` every spec carries.
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.
render_typesNoChart types a spec may name.
stock_assetsNoPresent when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto.
available_sourcesNoSource keys THIS account can use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: invalid spec entries are refused with the path of the problem, and available_sources is scoped to THIS account rather than a global catalog. It does not describe the response payload, but an output schema exists to carry that.

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 content is dense and front-loaded: what it returns, then when to call it, then the failure mode, then the account scoping. It is a long single sentence chain, so the prerequisite warning arrives mid-sentence rather than up front, which costs a point but not readability.

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?

With no parameters, full annotation coverage and an output schema, the description carries exactly the burden left to it: the scope of the catalog, the ordering requirement relative to preview_view and manage_view, and the refusal behavior. Nothing an agent needs in order to call it 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?

The tool takes zero parameters, so the baseline is 4, and the description explicitly confirms "Takes no arguments," removing any doubt about whether a source or account must be supplied.

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 names a specific resource (the schema for custom views) and enumerates exactly what it covers: data sources, per-source fields, formats, render types, ranges, caps, and the spec shape and rules. It also distinguishes itself from siblings by naming preview_view and manage_view as the consumers of this 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?

It states an explicit precondition: "Call this BEFORE writing a spec for preview_view or manage_view," and explains why — a spec can only name what this lists. That is a clear when-to-use rule tied to concrete alternative tools, with no inference required.

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.