Skip to main content
Glama

Live chart in the chat

show_chart
Read-only

Shows an interactive OwlChart candle chart inside the chat for any market (crypto, stocks, forex, commodities), with the liquidity magnets above and below drawn on it for crypto coins. Also returns the numbers.

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": {
      "symbol": "<symbol>"
    },
    "name": "show_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker or id, e.g. BTC, ETH, WLFI, AAPL, gold
intervalNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely non-structured behavior: the output is an interactive in-chat render, liquidity magnets are overlaid only for crypto coins, and the call also returns numeric data alongside the visual. It stops short of saying what those numbers actually contain.

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?

Two sentences, front-loaded with the core action and the asset scope, with the crypto-only caveat and the numeric return tacked on efficiently. The trailing 'Also returns the numbers' is loose phrasing that could be tightened but is not wasteful.

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

Completeness3/5

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

For a simple two-parameter tool with no output schema, the description covers what is rendered and that data comes back, but leaves the return payload ('the numbers') and the interval parameter unexplained. An agent can call it correctly, yet cannot predict the response shape without invoking it.

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 50%: symbol is documented while interval carries only an enum and default with no explanation. The description partly compensates by listing supported markets (crypto, stocks, forex, commodities) and noting crypto-specific liquidity magnets, which tells the agent what symbols are valid, but it says nothing about what the interval choices mean or how they affect the chart.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 (renders an interactive OwlChart candle chart in the chat) plus the asset scope (crypto, stocks, forex, commodities), which is far more than a restatement of the name. It does not explicitly contrast itself with data-only siblings like get_liquidity or get_liquidity_heatmap, so an agent must infer that this is the visual variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can deduce this is for when a visual chart is wanted rather than raw numbers. There is no explicit when-to-use/when-not-to-use statement and no named alternative, even though get_liquidity and get_liquidity_heatmap exist as plausible substitutes for liquidity information.

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