Clawallex MCP Server

get_card_balance

Retrieve current balance, currency, and status for a virtual card to monitor spending and manage online payments.

Instructions

Get the current balance and status of a virtual card. Only cards created by this agent (same client_id) are accessible. Returns available_balance, card_currency, status, and updated_at.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_card_balance"
  }
}

Input Schema

Name	Required	Description	Default
`card_id`	Yes	Card ID, e.g. 'c_123'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.7Mar 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full disclosure burden. It successfully documents the access control policy (same client_id restriction) and compensates for the missing output schema by listing specific return fields (available_balance, card_currency, status, updated_at). Minor gap: no error behavior described.

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?

Three sentences total, front-loaded with purpose, followed by access constraints, then return value documentation. No filler or redundant content; every clause provides necessary information not available in structured fields.

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 single-parameter read tool, the description adequately compensates for missing annotations and output schema by disclosing return structure and access restrictions. Would benefit from brief mention of error behavior (e.g., card not found) to be fully complete.

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?

Input schema has 100% description coverage (card_id with example format 'c_123'). Since the schema fully documents the parameter, the baseline score of 3 applies; the description does not need to add redundant parameter details.

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?

Description opens with specific verb 'Get' and clearly identifies the resource (current balance and status of a virtual card). It implicitly distinguishes from sibling batch_card_balances (single vs. multiple cards) and get_card_details (specific balance/status focus vs. general details).

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?

Provides clear access constraint ('Only cards created by this agent (same client_id) are accessible') which establishes when the tool is applicable. However, it does not explicitly name alternatives like batch_card_balances for bulk operations or differentiate from get_card_details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server