Skip to main content
Glama
Sign In
pay-mcp

pay-mcp

by MonadWorks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pay_balance

Check USDC balance on Base for your wallet or any specified address.

Instructions

Check USDC balance on Base. Returns the balance for your wallet or a specified address.

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

Input Schema

NameRequiredDescriptionDefault
addressNoAddress to check balance for. If not provided, returns your wallet balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool 'returns the balance' and implies a read-only operation via 'Check', but it does not explicitly state that it is non-mutating or describe behavior for invalid addresses or edge cases.

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, front-loaded sentence that efficiently conveys purpose and key parameter behavior without any wasted words.

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?

For a simple tool with one optional parameter, the description covers the core context: what it checks, on which network, and who it applies to. However, it does not describe the return format, which would be helpful given the absence of an output schema.

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 100% and the description adds meaning by explaining the optional address parameter ('your wallet or a specified address'). This reinforces the schema and clarifies the default behavior when no address is provided.

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 USDC balance on Base, which is a specific verb+resource. It distinguishes from sibling tools like pay_send, pay_request, and pay_history by focusing solely on balance checking.

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?

The description implies when to use this tool (to check USDC balance) and provides context about the Base network and optional address parameter. However, it does not explicitly mention alternatives or when not to use it, which would make it a 5.

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