Skip to main content
Glama

mcp-server

by io.github.tickerbot

tickerbot_get_ticker

Get the full current row for one ticker — every column on the schema (price, change, indicators like rsi_14, every boolean flag like above_sma_50, fundamentals like pe_ratio). Pass asof (YYYY-MM-DD or ISO timestamp like 2026-07-20T15:30:00Z) for the row as it stood at that past moment — date-only gives the close of that day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asofNoOptional YYYY-MM-DD or ISO timestamp. Date-only returns the row at close of that day; a timestamp returns the row as of that moment (finest tier covering each column).
tickerYesSymbol. Case-insensitive. Equities: bare symbol (AAPL). Crypto: X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs, not spot crypto.

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description explains the `asof` behavior (date-only vs timestamp) and what data is returned. It does not disclose potential error responses, rate limits, or idempotency, which would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two succinct sentences: first defines purpose and output, second covers the optional parameter. No filler, front-loaded with essential information.

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?

The description covers the main use cases (current and historical data), lists example columns, and explains ticker formats. Lacks mention of any edge cases (e.g., invalid ticker, data not available), but is otherwise complete given no output schema.

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%, but the description adds significant value: explains ticker format details (equities vs crypto) and clarifies `asof` behavior beyond the schema. This helps the agent use parameters correctly.

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 clearly states it retrieves the full current row for one ticker, listing example columns. It distinguishes from sibling tools like tickerbot_get_ticker_bars (historical bars) and tickerbot_get_ticker_history (history series) by focusing on the full current snapshot.

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?

Provides clear context on when to use the `asof` parameter for historical data and explains ticker format (equities vs crypto). However, lacks explicit guidance on when not to use this tool or direct comparison to other ticker-related tools.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct resource-action pairs, but get_ticker and get_ticker_history overlap (both return a single historical row via asof), and the four subscribe_* tools are thin wrappers around create_webhook, creating some ambiguity. Detailed descriptions mitigate but don't eliminate confusion.

Naming Consistency4/5

The tickerbot_ prefix and verb_noun pattern are consistent (create_*, get_*, list_*, delete_*, update_*), but subscribe_* deviates from create_* for webhooks, and scan/search_news are bare verbs. Overall predictable.

Tool Count2/5

35 tools is excessive for the domain; many could be consolidated (e.g., four subscribe_* variants into a single parameterized webhook creator, get_ticker/get_ticker_history into one). The breadth of data types justifies some volume, but this exceeds the 25-tool threshold for coherence.

Completeness5/5

Full lifecycle coverage for universes, custom signals, and webhooks; extensive read-side for tickers, series, bars, events, news, and scans. No critical dead ends: anything creatable can be updated/deleted/tested, and data lookups have appropriate query tools.

Resources