Skip to main content
Glama
Sign In
fletcher-agent

fletcher-agent

Official
by FletcherAgent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_trade_history

Retrieve closed trade history including PnL, entry/exit market cap, hold duration, strategy, and exit reason for Solana or Base chains.

Instructions

Get closed trade history with full PnL data, entry/exit mcap, hold duration, strategy, and exit reason

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trade_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain to filtersolana
limitNoNumber of trades to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so description carries burden. It implies read-only retrieval, but doesn't mention any behavioral aspects like pagination, authentication, or data freshness.

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?

Single sentence with no wasted words, front-loaded with purpose and key output fields.

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?

No output schema; description lists some fields but not all. For a simple 2-param tool, it's largely complete, but could detail return structure.

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?

100% schema coverage, description adds no extra meaning to parameters beyond what schema provides. Baseline 3.

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?

Description clearly states it retrieves closed trade history with specific data (PnL, mcap, hold duration, strategy, exit reason), and differs from sibling tools about agent state or token search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives. Context of sibling tools implies it's for historical trade data, but lacks guidance on when to prefer this over others.

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

Deploy Server

Other Tools