Skip to main content
Glama
Sign In
HeadlessTracker

HeadlessTracker

by tamasPetki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_custom_token

Remove a custom ERC-20 token from a MetaMask account's tracked tokens. Specify the account, chain, and contract address to untrack.

Instructions

Removes a custom ERC-20 token from a MetaMask account's tracked-tokens list. Public on-chain data, no keychain involvement. Use when the user asks: 'stop tracking ARB', 'remove that token from MetaMask', 'untrack a project token'. Inputs: - account_id: target MetaMask account (e.g. 'metamask:0xabc...') - chain_id: numeric (1=Ethereum, 137=Polygon, 56=BSC, 8453=Base, 42161=Arbitrum, 10=Optimism) - contract: 0x-prefixed contract address (40 hex) Returns ok or a not_found error if the token wasn't tracked under that account+chain.

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": {
      "account_id": "<account_id>",
      "chain_id": "<chain_id>",
      "contract": "<contract>"
    },
    "name": "remove_custom_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesTarget MetaMask account id (e.g. 'metamask:0xabc...').
chain_idYesEVM chain id the token is tracked on: 1=Ethereum, 137=Polygon, 56=BSC, 8453=Base, 42161=Arbitrum, 10=Optimism.
contractYesERC-20 contract address to untrack: 0x-prefixed, 40 hex chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.12

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses 'Public on-chain data, no keychain involvement' and describes return behavior (ok or not_found error). Sufficiently transparent for a simple removal operation.

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?

Concise, well-structured description at about 100 words. Includes overview, usage examples, parameter list, and return info without extraneous content.

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?

For a simple 3-param tool with no output schema and no annotations, the description fully covers purpose, usage, parameter details, and error handling. No gaps identified.

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

Parameters5/5

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

Schema coverage is 100% and description adds value beyond schema: provides example for account_id, lists common chain_id values, and specifies contract address format. Also explains return behavior, which is not in 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?

Description clearly states it removes a custom ERC-20 token from a MetaMask tracked-tokens list. Provides specific verb and resource, and example user queries. Distinguishes from sibling tools like add_custom_token and list_custom_tokens.

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?

Explicitly says 'Use when the user asks...' with concrete examples (e.g., 'stop tracking ARB'). Does not explicitly mention when not to use, but the examples make it clear.

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