get_ticker
Get real-time price snapshots for one or more symbols.
Returns last price, 24h volume, 24h high/low, price change and percent change.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| symbols | Yes |
TickDB Market Data
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses it is real-time and lists returned data, but with no annotations (readOnly, destructive) it does not fully carry the burden. Missing details on rate limits, permission requirements, or whether partial data is returned for invalid symbols.
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 description is two sentences with no extraneous text. The structure is efficient, though it could benefit from a brief note on parameter usage.
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?
Given the moderate complexity (2 params, simple output), the description adequately covers the tool's core purpose and output. Without an output schema, listing return fields is helpful, although it omits page/errors handling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, and the description only explains that `symbols` accepts one or more symbols (implicitly). The optional `type` parameter is not mentioned at all, leaving its purpose undocumented.
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 the tool retrieves real-time price snapshots for one or more symbols and lists specific return fields (last price, volume, high/low, changes). This is distinct from sibling tools like get_kline (historical), get_order_book (order depth), etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as get_intraday or get_kline. It lacks context about typical use cases or scenarios where this tool is preferable.
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.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct data type or operation (e.g., symbol discovery, capital flow, intraday, kline, order book, trades). No two tools have overlapping purposes, and descriptions clearly differentiate them.
Naming Consistency5/5
All tools follow a consistent 'get_' prefix followed by a descriptive noun (e.g., get_available_symbols, get_intraday, get_kline). No mixing of conventions or vague verb usage.
Tool Count5/5
13 tools is well-scoped for a market data server. Each tool serves a specific need without unnecessary redundancy, covering discovery, real-time, historical, and reference data.
Completeness4/5
The tool set covers core market data needs: discovery, real-time quotes, historical kline, depth, trades, capital flow, metrics, trading calendar, and sessions. Minor gaps exist (e.g., corporate actions, historical trade list), but the primary workflows are supported.