Skip to main content
Glama

Stocktwits

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Chart Data

chart_data
Read-onlyIdempotent

"Chart data for [ticker]" / "sparkline data for [stock]" / "price history for [ticker] this week" — OHLCV price bars for a ticker from the StockTwits chart feed: 5-minute bars for one trading day (1D), ~30-minute bars for a week (1W), daily bars for 1M/3M/6M/YTD, weekly for 1Y, monthly for 5Y/ALL. Returns open, high, low, close and volume per bar. Crypto uses the StockTwits suffix (BTC.X). Use for thumbnail charts and quick recent-price context beside StockTwits sentiment; prefer dedicated finance packs (yahoo-finance, alphavantage) for serious price analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoChart window (default 1D). Case-insensitive.
symbolYesTicker without the $ (AAPL, TSLA; BTC.X for Bitcoin).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "symbol": "AAPL"
-  },
-  {
-    "period": "1d",
-    "symbol": "GME"
-  }
-]New value: +[
+  {
+    "symbol": "AAPL"
+  },
+  {
+    "period": "1W",
+    "symbol": "TSLA"
+  }
+]
    • addedInput schema / properties / period / description
      Added value: +"Chart window (default 1D). Case-insensitive."
    • addedInput schema / properties / period / enum
      Added value: +[
+  "1D",
+  "1W",
+  "1M",
+  "3M",
+  "6M",
+  "YTD",
+  "1Y",
+  "5Y",
+  "ALL"
+]
    • addedInput schema / properties / symbol / description
      Added value: +"Ticker without the $ (AAPL, TSLA; BTC.X for Bitcoin)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "symbol": "AAPL"
+  },
+  {
+    "period": "1d",
+    "symbol": "GME"
+  }
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, but the description adds substantial context beyond them: the bar granularity per period (5-min, ~30-min, daily, weekly, monthly) and crypto ticker convention (BTC.X). It stops short of describing pagination or limits, but for a read-only feed call this is rich.

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?

Front-loaded with query-intent phrases and then dense, useful detail. Every clause carries information, though the three leading quoted phrasings are slightly redundant with each other.

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 output schema, the description carries the return-format burden and does so ('open, high, low, close and volume per bar'). Combined with granularity and alternative routing, an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds real meaning by explaining what each enum window represents in terms of bar resolution, and by specifying the crypto suffix convention for symbol. This goes beyond the schema's bare enum list.

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 resource (OHLCV price bars for a ticker from the StockTwits chart feed) with the exact cadence per window. It is immediately distinguishable from siblings like company_facts or symbol_search, which return different resources.

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?

Explicitly names the intended use ('thumbnail charts and quick recent-price context beside StockTwits sentiment') and routes serious price analysis to named alternatives (yahoo-finance, alphavantage). Both when-to-use and when-to-prefer-another are covered.

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

All Stocktwits toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources