Skip to main content
Glama
Sign In
TerraDeed MCP Server

TerraDeed MCP Server

Official
by terradeed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

terradeed_check_wallet

Check USDC balance on Base mainnet for any Ethereum address. Free, no payment required.

Instructions

Check the USDC balance of a wallet on Base mainnet. Free — no x402 payment required.

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

Input Schema

NameRequiredDescriptionDefault
addressNoEthereum address to check (defaults to the payment wallet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It adds key context by specifying that the tool is free (no x402 payment required) and operates on Base mainnet. It does not explain error handling or return format, but for a simple read-only balance check, this is acceptable.

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?

The description is a single sentence that front-loads the core purpose and includes only essential additional context (free, network). Every word contributes to understanding.

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?

The tool is simple: one optional parameter, no output schema, no annotations. The description provides sufficient information to know what the tool does, under what conditions (free, Base mainnet), and implies the output is the balance. This is complete for a tool of this complexity.

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?

The schema provides a complete description for the address parameter (including default behavior), achieving 100% coverage. The description adds no additional parameter-level information, so the baseline score of 3 is appropriate.

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 the tool checks the USDC balance of a wallet on Base mainnet, using a specific verb and resource. It also distinguishes itself from sibling tools by focusing on wallet balance rather than URL scraping or structured extraction.

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 description implies its usage by explaining it checks wallet balance and is free, but it does not explicitly state when to use it over alternatives. The sibling tools are clearly for different purposes, so the intended use is inferred rather than explicitly stated.

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