Skip to main content
Glama

TickDB Market Data

by io.github.TickDB
OverviewDiscussionsAdmin

get_market_metrics

Get comprehensive market metrics and valuation data for stocks.

    Returns: price, change, volume, turnover, YTD change, turnover rate, market cap,
    capital flow, PE (TTM), PB ratio, dividend yield, 5/10/180-day price change rates.
    Supported: US stocks, Hong Kong stocks, A-shares.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct type for disambiguation: stock, crypto, forex, indices
symbolsYesComma-separated stock codes, max 50. E.g. '700.HK,AAPL.US'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbols / description
      Added value: +"Comma-separated stock codes, max 50. E.g. '700.HK,AAPL.US'"
    • addedInput schema / properties / type / description
      Added value: +"Product type for disambiguation: stock, crypto, forex, indices"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned field set and supported markets, but says nothing about permissions/auth, rate limits, error behavior for unsupported symbols, or that the tool is read-only — gaps that matter for a tool with zero annotation coverage.

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 purpose followed by a returns list and a supported-markets note. The field enumeration is long but justified as a substitute for the absent output schema, and there is little waste.

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?

With no annotations and no output schema, the description supplies the return values and market coverage, which partly offsets those gaps. However, it omits usage context, auth/limit behavior, and how unsupported types are handled, leaving it only minimally complete for an agent to call it correctly.

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 description coverage is 100%, with the schema documenting both the symbols format (comma-separated, max 50, example given) and the type disambiguation values. The description's only added parameter context is the supported market list, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Get comprehensive market metrics and valuation data for stocks') and enumerates the fields returned. It is clear, but it never explicitly distinguishes itself from narrower siblings such as get_valuation_latest or get_capital_flow, so sibling differentiation is left to inference.

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?

The description gives no when-to-use guidance and names no alternatives. 'Supported: US stocks, Hong Kong stocks, A-shares' is a coverage note, not usage direction, leaving the agent to guess when this tool beats its many siblings.

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

All TickDB Market Data 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