Skip to main content
Glama
n1n4du

MTRKR MCP Server

by n1n4du
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

mtrkr_companion_get

Retrieves a wallet's activity snapshot for a specific Terminal campaign wave, showing app usage, token flows, timeline, and coaching insights. Resolves .mega names.

Instructions

Wallet transaction analytics: focused on the MegaETH Terminal bonus campaign as a wave-to-wave companion (latest interactions per selected wave, coaching-style output)—not official campaign scoring. MTRKR + Blockscout; campaign waves use explicit startDate/endDate in config (e.g. wave 1: 2026-04-28–2026-05-05). API still labels responses with wave* field names. strategyProfile is heuristic, not official bonus math. Analyzer API v2026.04+: EOAs that received native ETH or ERC-20 from the primary wallet in the pre-period funding lookback appear in linkedWallets; their outbound txs in that window merge into totals, token flow attribution, timeline, and waveTransactionLedger (each row has originWallet; waveTransactionLedgerMeta.linkedWalletsMerged). In currentWave, waveTransactionLedger lists each outbound tx in the period (newest-first cap in meta): action, summary, swaps/bridges/transfers via decoder, plus terminalAppKey when to matches a tracked app contract. outboundTxCountInWave counts all merged outbound txs in the window; terminalMatchedOutboundTxCount / usedApps are tracked-contract attribution only. GET snapshot for one wallet: usage vs tracked apps in the selected Terminal wave from campaign config, timeline, token flows, coaching text, and waveResolved meta. Period selection: optional wave string (e.g. last_completed, current, or numeric id like 005), optional whichWave, optional waveId. Resolves .mega names. Does not accept user points — use mtrkr_companion_analyze for pointsAlignment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesWallet 0x address or .mega name
waveNoPeriod selector: last_completed | current | numeric wave id (Terminal campaign calendar)
waveIdNoNumeric period id (API field `waveId`; merged with `wave` string if both set)
whichWaveNoPick current or last completed Terminal wave when not using numeric wave id

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

With no annotations, the description discloses heuristic nature of strategyProfile, wave configuration, linkedWallets behavior, and what the output includes. Does not claim read-only or side effects, but overall transparent about campaign context and API behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose but overly verbose with technical details on wave configuration, linkedWallets, and output structure. Could be more concise while retaining key guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description thoroughly explains campaign wave system, parameter selection, linked wallet merging, and output components (waveTransactionLedger, token flows, coaching text). Links to sibling tool completes context.

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 coverage is 100% with good descriptions. The description reiterates parameter options and adds minor context on merging behavior and .mega resolution, but adds marginal value over schema.

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 explicitly states the tool provides wallet transaction analytics focused on the MegaETH Terminal bonus campaign as a wave-to-wave companion, clearly distinguishes it from sibling tool 'mtrkr_companion_analyze' for points, and specifies a snapshot for one wallet with usage, timeline, token flows, and coaching text.

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

Usage Guidelines4/5

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

Provides guidance on period selection (wave, whichWave, waveId) and explicitly states not to use for points—directs to sibling tool. Lacks explicit 'when not to use' but clearly defines context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/n1n4du/mtrkr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server