Skip to main content
Glama

Stop tracking wallet address

remove_wallet_address
DestructiveIdempotent

Stop tracking a wallet address for this account, on every chain it covers, so balances, portfolio value and DeFi positions no longer include it. Accepts a 0x EVM address, a .eth ENS name (resolved before matching) or a Sui address. Returns the removed entry; fails with "not tracked" when the address is not tracked. Only affects this account's own tracked-address list.

Input Schema

NameRequiredDescriptionDefault
addressYes

Output Schema

NameRequiredDescriptionDefault
addressYes
ensNameNo
removedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / chain
      Removed value: -{
      -  "description": "Chain id: a numeric EVM chain id, or sui_mainnet; tracked chains are 1 Ethereum, 56 BNB Chain, 8453 Base, 42161 Arbitrum, sui_mainnet Sui",
      -  "type": "string"
      -}
    • addedOutput schema / properties / removed / additionalProperties
      Added value: +false
    • removedOutput schema / properties / removed / items
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "address": {
      -      "type": "string"
      -    },
      -    "chain": {
      -      "type": "string"
      -    },
      -    "chainName": {
      -      "type": "string"
      -    },
      -    "createdAt": {
      -      "type": "number"
      -    },
      -    "id": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "id",
      -    "chain",
      -    "address",
      -    "createdAt",
      -    "chainName"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / removed / properties
      Added value: +{
      +  "address": {
      +    "type": "string"
      +  },
      +  "chains": {
      +    "items": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "chain": {
      +          "type": "string"
      +        },
      +        "chainName": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "chain",
      +        "chainName"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "createdAt": {
      +    "type": "number"
      +  },
      +  "family": {
      +    "enum": [
      +      "evm",
      +      "sui"
      +    ],
      +    "type": "string"
      +  },
      +  "id": {
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / removed / required
      Added value: +[
      +  "id",
      +  "family",
      +  "address",
      +  "chains",
      +  "createdAt"
      +]
    • changedOutput schema / properties / removed / type
      Previous value: -"array"New value: +"object"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description adds real value on top by naming what is destroyed (balances, portfolio value, DeFi positions), the all-chains blast radius, the error behavior, and the account-level blast radius ("Only affects this account's own tracked-address list"). Minor gap: with idempotentHint=true an agent might expect a no-op repeat, but the description says a repeat call errors — that nuance could be spelled out rather than omitted.

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?

Three sentences, each load-bearing and front-loaded with the action; scope, inputs, return and failure are packed in without filler.

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?

A destructive single-param mutation with an output schema: the description covers the side effects, input formats, error case and account scoping. An agent has everything needed to invoke it correctly and warn the user about consequences.

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?

Schema coverage is 0% (only type and maxLength=255), so the description must carry the load — and it does, enumerating three accepted forms: 0x EVM, .eth ENS (resolved before matching), and Sui addresses. It omits checksum/case-sensitivity or malformed-address behavior, so not fully exhaustive.

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?

Specific verb+resource ("Stop tracking a wallet address") with explicit scope ("on every chain it covers") and the downstream effect on balances, portfolio value and DeFi positions. Clearly the inverse of add_wallet_address and distinct from list_wallet_addresses.

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?

Usage context is clear: remove an address the user no longer wants tracked, with the failure condition ("not tracked") spelled out. It does not explicitly name add_wallet_address as the counterpart action, so a small inference remains, but no wrong-tool ambiguity is created.

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.