Skip to main content
Glama
Sign In
HeadlessTracker

HeadlessTracker

by tamasPetki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_accounts

List configured crypto exchange and wallet accounts (Bybit, Binance, MetaMask, Polymarket, Solana) without revealing credentials. Filter by connector type.

Instructions

Lists configured PORTFOLIO TRACKER accounts (Bybit exchange / Binance exchange / MetaMask wallets / Polymarket / Solana wallets) without exposing credentials. Use when the user asks: 'what tracker accounts are configured', 'show my portfolio accounts', 'list my exchange connections', 'which crypto exchanges are linked'. Returns: id, connectorId (bybit | binance | metamask | polymarket | solana), label, createdAt, and connector-specific public metadata (e.g. chainIds and addresses for MetaMask, accountType for Bybit, address for Solana, key fingerprint for Binance). Credentials are NEVER returned — they stay in the OS keychain. DO NOT call this tool when the user means: email accounts, social media accounts, GitHub accounts, cloud accounts, OS user accounts, or any 'accounts' from a different domain or MCP server. It's specifically the headless-tracker exchange/wallet connections.

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": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectorNoFilter to accounts of one connector. Omit to list every configured account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.12

TDQS

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses that credentials are never returned and stay in the OS keychain, and lists the exact fields returned (id, connectorId, label, createdAt, connector-specific metadata).

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?

The description is informative with multiple sentences, but all content is necessary. Front-loaded with the tool's purpose and examples. Slightly verbose but no redundancy.

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?

Given the tool's simplicity (one optional parameter, list operation), the description fully covers behavior, return fields, and usage boundaries. Without an output schema, the description compensates with detailed return info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The optional 'connector' parameter is explained in the description (omit for all accounts, include to filter), adding context beyond the enum list. Schema coverage is 100%, so baseline 3; the description adds clear usage guidance.

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 clearly states it lists configured PORTFOLIO TRACKER accounts (specific exchange/wallet types) and distinguishes from sibling tools by explicitly excluding unrelated account types (email, social media, etc.).

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

Usage Guidelines5/5

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

Provides explicit usage examples (user queries) and states when NOT to use the tool (other account domains), giving clear guidance on when to invoke this tool vs alternatives.

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