trader_get_trade_history
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| payment | No | ||
| auth_token | No | ||
| twitter_handle | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
MangroveTrader
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
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?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
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
C2/5.0
Disambiguation4/5
Most tools have distinct purposes targeting different trader-related actions like login, watching, searching, and reporting. However, 'trader_last_trade' and 'trader_cancel_last' could potentially overlap if 'last_trade' refers to a recent trade that might be canceled, creating minor ambiguity in their boundaries.
Naming Consistency5/5
All tool names follow a consistent 'trader_' prefix with snake_case, using clear verbs like get, search, watch, and login. This predictable pattern makes the set easy to navigate and understand at a glance.
Tool Count5/5
With 10 tools, this server is well-scoped for a trading domain, covering authentication, monitoring, reporting, and data retrieval. Each tool appears to serve a specific function without redundancy, making the count appropriate for the apparent purpose.
Completeness3/5
The tools cover authentication, monitoring, and reporting well, but there are notable gaps in core trading operations. For a trader server, obvious missing actions include executing trades, managing orders, or accessing market data, which limits the surface for full trading workflows.