@dfm-fi/agent

Official

by DFM-Finance

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Follow a trader

follow_trader

Idempotent

Monitor a trader by Solana wallet address to track their onchain activity; no funds are moved.

Instructions

Follow a trader by wallet address. Moves no funds.

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": {
      "wallet": "<wallet>"
    },
    "name": "follow_trader"
  }
}

Input Schema

Name	Required	Description	Default
`wallet`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1967Oct 20, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false (implying a state mutation) plus idempotentHint and openWorldHint. The description adds genuinely useful context beyond those flags: 'Moves no funds' reassures the agent that this write-like action has no financial side effects, resolving ambiguity created by readOnlyHint=false.

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?

Two short sentences, zero filler, with the core action stated first and the safety clarifier second. Every sentence earns its place.

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?

For a low-complexity, single-parameter tool with no output schema, the description plus annotations cover the essential facts an agent needs. Minor gaps remain around what following actually changes and any relationship to trader_profile.

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 0% for the single required parameter, so the description carries the burden. 'By wallet address' clarifies that the wallet param is a wallet address rather than an ID or name, which compensates somewhat but stops short of format or length guidance.

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?

'Follow a trader by wallet address' gives a specific verb and resource, and the 'wallet address' qualifier tells the agent what identifier is expected. The contrast with the sibling unfollow_trader is inferable from the name but is not stated in the description.

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 offers no when-to-use or when-not-to-use guidance, and it never points the agent at alternatives such as trader_profile or unfollow_trader. Usage must be inferred entirely from the tool name.

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