Skip to main content
Glama
listingbureau

Listing Bureau - Amazon Organic Ranking

lb_wallet_get_balance

Read-only

Retrieve your current wallet balance in credits and USD, including alerts for temporary data unavailability.

Instructions

Get Listing Bureau wallet balance (credits and USD). May include a warning if data is temporarily unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for lb_wallet_get_balance tool. Calls client.request('GET', '/api/v1/wallet') to fetch wallet balance, then formats the result via formatResult(). On error, returns an error result via formatErrorResult().
      async () => {
        try {
          const res = await client.request<WalletBalance>(
            "GET",
            "/api/v1/wallet",
            undefined,
            undefined,
            "lb_wallet_get_balance",
          );
          return formatResult(res.data);
        } catch (e) {
          return formatErrorResult(e);
        }
      },
    );
  • Registration of the 'lb_wallet_get_balance' tool via server.tool(). The tool has no input schema (empty object {}) and is marked readOnlyHint: true. It's registered inside registerWalletTools() which is called from src/index.ts line 57.
    export function registerWalletTools(server: McpServer, client: LBClient) {
      server.tool(
        "lb_wallet_get_balance",
        "Get Listing Bureau wallet balance (credits and USD). May include a warning if data is temporarily unavailable.",
        {},
        { readOnlyHint: true  },
        async () => {
          try {
            const res = await client.request<WalletBalance>(
              "GET",
              "/api/v1/wallet",
              undefined,
              undefined,
              "lb_wallet_get_balance",
            );
            return formatResult(res.data);
          } catch (e) {
            return formatErrorResult(e);
          }
        },
      );
  • The WalletBalance interface defines the response type for this tool: balance_usd (number) and held_usd (number).
    export interface WalletBalance {
      balance_usd: number;
      held_usd: number;
    }
  • The formatResult() helper used to format the wallet balance data into an MCP CallToolResult, including extraction of warning/balance_warning fields.
    export function formatResult(data: unknown): CallToolResult {
      const warnings: string[] = [];
      let cleaned: Record<string, unknown> | unknown = data;
    
      if (data && typeof data === "object") {
        const obj = { ...(data as Record<string, unknown>) };
    
        // Top-level warning string
        if ("warning" in obj && typeof obj.warning === "string") {
          warnings.push(obj.warning);
          delete obj.warning;
        }
    
        // balance_warning object (independent of warning)
        if ("balance_warning" in obj && obj.balance_warning && typeof obj.balance_warning === "object") {
          const bw = obj.balance_warning as Record<string, unknown>;
          const parts: string[] = [];
          if (typeof bw.warning === "string" && bw.warning.trim()) parts.push(bw.warning);
          if (typeof bw.daily_cost_estimate === "number")
            parts.push(`Daily cost estimate: $${bw.daily_cost_estimate.toFixed(2)}`);
          if (typeof bw.balance === "number")
            parts.push(`Balance: $${bw.balance.toFixed(2)}`);
          if (typeof bw.days_remaining === "number")
            parts.push(`Days remaining: ${bw.days_remaining.toFixed(1)}`);
          if (parts.length > 0) warnings.push(parts.join(" | "));
          delete obj.balance_warning;
        }
    
        cleaned = obj;
      }
    
      let text = JSON.stringify(cleaned, null, 2);
      for (const w of warnings) {
        text += `\n\n⚠️ Warning: ${w}`;
      }
    
      const notice = getUpdateNotice();
      if (notice) {
        text += `\n\n${notice}`;
      }
    
      return {
        content: [{ type: "text", text }],
      };
    }
  • The LBClient.request() method that performs the authenticated HTTP request. For this tool, it makes a GET request to /api/v1/wallet with the tool name 'lb_wallet_get_balance' in the X-LB-Tool header.
    async request<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      query?: Record<string, string>,
      toolName?: string,
    ): Promise<ApiSuccessResponse<T>> {
      await this.ensureAuth();
      const response = await this.doRequest<T>(method, path, body, query, toolName);
    
      // Single retry on 401
      if (response.status === "error" && response._statusCode === 401) {
        this.jwt = null;
        await this.ensureAuth();
        const retry = await this.doRequest<T>(method, path, body, query, toolName);
        if (retry.status === "error") {
          throw new LBApiError(
            retry._statusCode ?? 500,
            retry.error.code,
            retry.error.message,
          );
        }
        return retry as ApiSuccessResponse<T>;
      }
    
      if (response.status === "error") {
        throw new LBApiError(
          response._statusCode ?? 500,
          response.error.code,
          response.error.message,
        );
      }
    
      return response as ApiSuccessResponse<T>;
    }
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds value by mentioning a potential warning if data is temporarily unavailable, informing the agent of possible non-standard behavior beyond the annotation.

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?

Two concise sentences that are front-loaded with the core action and include relevant details without waste. Every sentence earns its place.

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?

Given no parameters and no output schema, the description fully covers the tool's purpose, return values, and a potential edge case (warning). It is complete for its complexity level.

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?

No parameters exist, so schema coverage is 100%. Description adds meaning by specifying what the tool returns (credits and USD) and a warning, which is sufficient for zero-parameter tools.

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 clearly states 'Get Listing Bureau wallet balance' with specifics 'credits and USD', making the purpose unambiguous and distinct from sibling tools like 'lb_wallet_get_transactions'.

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?

No explicit when-to-use or alternatives are provided, but the simple nature of the tool implies usage for checking balance. Context is clear but lacks guidance on exclusions or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/listingbureau/listingbureau-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server