Skip to main content
Glama

List the finance charts

list_finance_charts
Read-onlyIdempotent

Lists available chart types such as bars, donut, scatter, heatmap, and equity curve with class names and purposes; search by chart name or use case.

Instructions

Lists the charts of @tradecanvas/chart that are not the trading chart: bars, donut, scatter, histogram, calendar, correlation matrix, heatmap and sector map, depth, equity curve, waterfall, gauge, sparkline, and a backtest dashboard. Each with its class name and what it is for; list_options with that name gives its options. Search by words of the name or the purpose.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords to find in the name or the purpose, e.g. "order book" or "returns".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds real context beyond that: the result set explicitly excludes the trading chart, each entry carries a class name plus purpose text, and the query does word-level matching over name or purpose. Missing are result-count or ordering details.

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 scope come first, then the chaining hint, then the search behavior — good front-loading. The long enumeration of chart types is the one cost: it is informative but inflates the sentence and duplicates what a listing call would return.

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?

For a read-only listing tool with a fully documented single optional parameter and clear annotations, the description supplies what's needed: scope, what each entry contains, and the follow-up call to get options. Return size and ordering are the only meaningful omissions, and no output schema exists to cover them.

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?

Schema coverage is 100% and the single optional parameter already documents that words are matched against name or purpose. The description's 'Search by words of the name or the purpose' restates the schema rather than adding format or matching-rule detail, so this lands at the high-coverage baseline.

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 ('Lists the charts of @tradecanvas/chart') and immediately scopes it by excluding the trading chart, then enumerates the included chart families (bars, donut, scatter, heatmap, depth, equity curve, etc.). An agent can distinguish it from the trading-chart tooling without opening the 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 says how to use the tool ('Search by words of the name or the purpose') and, critically, routes the agent onward: 'list_options with that name gives its options.' What it lacks is an explicit when-not-to-use condition, e.g. whether there is a separate path for trading-chart options.

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