Skip to main content
Glama
yg-base-mcp
by ufo1898

wallet

Checks a Base address for balances, yield positions, Moonwell withdrawability, gas runway, and risk flags.

Instructions

任意 Base 钱包体检:余额、生息位置、Moonwell 能不能取出、gas 续航、风险清单(?address=0x…) — 0.010 USDC per call (x402, Base USDC, no signup)

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase address 0x…
_paymentNobase64 PAYMENT-SIGNATURE from a previous 402 challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the two things an agent most needs beyond the schema: the price (0.010 USDC per call), the payment rail (x402 on Base USDC), and that no signup is required. It stops short of stating the operation is read-only, what happens on payment rejection, or any rate/latency limits, so it is strong but not exhaustive.

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?

One dense sentence front-loads the scope, then the coverage list, then the price and payment terms, with no filler. The nested parentheses and run-on list slightly reduce scannability, but nothing is redundant.

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

Completeness4/5

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

There is no output schema, and the enumeration of inspected areas (balance, yield positions, Moonwell withdrawability, gas runway, risk list) effectively signals what comes back. Payment mechanics are covered. Only the fact that payment is required upfront via a 402 challenge could be spelled out more explicitly for a first-time caller.

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%: both 'address' (Base address 0x…) and '_payment' (base64 PAYMENT-SIGNATURE from a 402 challenge) are already documented in the schema. The description's '(?address=0x…)' only echoes the schema's address format, adding no new semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete subject (任意 Base 钱包体检) and enumerates exactly what is inspected: balance, yield-bearing positions, Moonwell withdrawability, gas runway, and a risk checklist. That is far more specific than the bare name 'wallet'. It does not differentiate from siblings such as 'pools', 'yields', or 'tokenrisk', which look adjacent, so it falls short of a 5.

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?

Usage is implied: call this for a broad health check of a Base wallet across several dimensions at once. There is no statement of when to prefer a narrower sibling, no prerequisite conditions beyond payment, and no exclusions. Adequate but leaves the agent to infer routing.

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