Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Instances Customers Wallets Balance

GetV1InstancesCustomersWalletsBalance
Read-onlyIdempotent

Retrieves a customer's BlindPay-managed wallet balance on Base for USDC, USDT, USDB and EURC/EURB, returning whole-token amounts and yield-inclusive totals.

Instructions

Returns the balance of a BlindPay-managed wallet for USDC, USDT and USDB, plus EURC (EURB on development instances) on Base. Unlike quote and payout amounts, these values are whole tokens, not cents: amount 10.5 means 10.5 USDC. total_amount is amount plus earning_amount from yield.

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": {
      "instance_id": "<instance_id>",
      "customer_id": "<customer_id>",
      "id": "<id>"
    },
    "name": "GetV1InstancesCustomersWalletsBalance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
customer_idYesCustomer ID
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.3

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds genuinely useful behavioral context absent from structured fields: values are whole tokens (10.5 = 10.5 USDC) not cents, and total_amount includes earning_amount from yield. It does not say how dev vs prod affects EURB beyond a parenthetical, but overall it earns credit above the annotation baseline.

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?

Front-loaded with what is returned, then the high-value unit caveat, then the total_amount definition. Three dense sentences with little waste, though the token-list enumeration is slightly crowded.

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

Completeness3/5

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

For a read-only tool with no output schema, the description does well explaining return semantics (units, total_amount). However, with a thin schema it leaves the required identifier parameters unexplained, which is a real completeness gap for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — customer_id is documented but id and instance_id are bare strings with just examples. The description adds no meaning for any of the three required parameters, leaving the agent to infer that 'id' is the wallet identifier from the tool name alone.

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?

States a specific verb and resource: returns wallet balance for named tokens (USDC, USDT, USDB, EURC) on Base. An agent can tell this is a balance-read tool distinct from the wallet-list/CRUD siblings, though it never names an explicit alternative.

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 only implied by the resource itself (get a wallet's balance). There is no explicit 'use this when X, not Y' guidance, and no mention of prerequisites such as whether the customer wallet must exist or be yield-enabled.

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