get_recent_trades
Get the most recent executed trades for a symbol.
Returns trade id, price, quantity, side (buy/sell), and timestamp.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| symbol | Yes |
TickDB Market Data
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It only states it returns recent trades but does not disclose if it's read-only, auth needs, rate limits, or error behavior.
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 clear sentences with no waste. First sentence states purpose, second lists output fields. Could combine but still concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description must explain return values. Partially covers fields but omits details on 'recent', default limit, or pagination. Incomplete for a tool with 3 parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, and the description adds no meaning to the three parameters. It only mentions 'symbol' implicitly but does not explain 'type' or 'limit'.
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 gets the most recent executed trades for a symbol, listing the returned fields. This differentiates it from siblings like get_order_book or get_ticker.
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 on when to use this tool versus alternatives. There is no mention of limitations, recency period, or when not to use it, leaving the agent without decision context.
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.