Skip to main content
Glama

Copy-trade signals

copy_trade_signals
Read-only

Analyze a wallet's recent swap activity for copy trading. Returns active positions, buy/sell patterns, entry prices, and trading frequency. Costs $0.01 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "walletAddress": "<walletAddress>"
    },
    "name": "copy_trade_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesSolana wallet address to analyze (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious context by stating the exact cost ('$0.01 USDC per call'), which the schema and annotations cannot convey, and it previews the return shape. It stops short of stating a lookback window for 'recent' or any rate/throughput limits.

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?

Three short sentences, front-loaded with the core action and closing with the cost disclosure, with no filler. It is arguably one clause short of ideal because 'recent' is left unquantified rather than used to add precision.

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 output schema, the description does its part by naming the returned data, and it covers cost. However, for an analysis tool the key missing piece is scope: how far back 'recent' reaches, whether a wallet with no swaps returns an empty result, and whether the tool works on any Solana wallet or only active traders. Those gaps matter for correct invocation.

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?

There is one parameter with 100% schema description coverage ('Solana wallet address to analyze (base58)'), so the schema already carries the semantics. The description only reiterates 'a wallet's recent swap activity' without adding format, constraints, or behavior for the parameter — baseline 3 applies.

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: 'Analyze a wallet's recent swap activity for copy trading,' and enumerates what it returns (positions, buy/sell patterns, entry prices, frequency). It is distinguishable from data siblings like wallet_pnl or wallet_profile, but it never explicitly names those alternatives, so differentiation relies on inference.

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?

The phrase 'for copy trading' implies the use case, but there is no explicit when-to-use guidance and no routing rule against close siblings such as wallet_pnl, smart_money, or top_traders. An agent must guess which wallet-analysis tool fits which question.

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.

Resources