Skip to main content
Glama
Sign In
Agent Kiosk

Agent Kiosk

by ralf9090
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wallet_profiler

Read-onlyIdempotent

Profile any 0x EVM wallet across Base, Ethereum, Arbitrum, and Polygon to check live USDC, ETH/POL balances, nonce, wallet tier, and contract vs EOA status.

Instructions

Multi-chain whale & wallet portfolio profiler across Base, Ethereum, Arbitrum, and Polygon. Returns live USDC and native ETH/POL balances, total outgoing transaction counts (nonce), wallet tier (Whale/Trader/Retail), and smart contract vs EOA detection.

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": {
      "address": "<address>"
    },
    "name": "wallet_profiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x... 40-hex EVM wallet or contract address to profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and idempotency are covered externally. The description adds genuine behavioural value by disclosing the live-data nature of the response and the four supported chains. It stops short of noting rate limits or freshness/caching behaviour.

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 dense sentences with zero filler. The resource and chain scope lead, and the return payload follows immediately, so the most decision-relevant information is front-loaded.

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?

With no output schema, the description carries the burden of explaining return values and does so exhaustively (balances, nonce, tier classification, contract detection). For a one-parameter, read-only tool of low complexity, nothing an agent needs to call it correctly is missing.

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 100% for the single 'address' parameter, and the schema already specifies the 0x 40-hex EVM format. The description contributes no additional parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 names a specific verb and resource ('Multi-chain whale & wallet portfolio profiler') and enumerates the exact outputs: USDC/native balances, nonce, wallet tier, and EOA-vs-contract detection. No sibling tool (academic_search, defi_yields, etc.) overlaps this scope, so an agent can route here unambiguously.

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

Usage Guidelines3/5

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

The stated outputs imply the use case (profiling a wallet address for balance and behavioural signals), but there is no explicit when-to-use, when-not-to-use, or named alternative. Chains covered are listed, which is helpful context, but selection guidance is left to inference.

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