Skip to main content
Glama

gpu_balance

Check GPU-Bridge credit balance, daily spending, volume discount tier, and job history for AI compute services.

Instructions

Check GPU-Bridge credit balance, daily spend, volume discount tier, and job history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'gpu_balance' tool, which fetches account balance data from the API and formats it into a text response.
          case "gpu_balance": {
            const balance = await apiCall("/account/balance", "GET");
            const vd = balance.volume_discount || {};
            let text = `Balance: $${balance.balance}
    Daily spend: $${balance.daily_spend}/$${balance.daily_limit}
    Tier: ${vd.tier} (${vd.discount_percent}% discount)`;
            if (vd.next_tier) {
              text += `
    Next tier: ${vd.next_tier.name} at $${vd.next_tier.threshold} spent (${vd.next_tier.discountPercent}% discount)`;
            }
            return { content: [{ type: "text", text }] };
          }
  • index.js:56-60 (registration)
    The definition and registration of the 'gpu_balance' tool in the tool list provided to the MCP server.
    {
      name: "gpu_balance",
      description: "Check GPU-Bridge credit balance, daily spend, volume discount tier, and job history.",
      inputSchema: { type: "object", properties: {} }
    },
Behavior3/5

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

No annotations provided, so description carries full burden. Lists four specific data categories returned (good), but omits operational details: no mention of authentication requirements, rate limits, pagination for job history, or whether data is real-time vs cached.

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?

Single sentence, front-loaded with action verb. No filler words. Every clause specifies a distinct data category returned. Optimal density.

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 parameterless account-query tool without output schema, listing the four return data categories provides adequate completeness. Missing only operational metadata (Auth, TTL) which would be nice-to-have but not critical for this 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?

Zero parameters present per schema. With no parameters to document, baseline score applies.

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?

Specific verb 'Check' and concrete resources listed (credit balance, daily spend, volume discount tier, job history). While distinct from siblings (gpu_run, gpu_status, etc.) by nature of the data, the description does not explicitly differentiate usage scopes in text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this versus siblings (e.g., 'Check this before running jobs with gpu_run' or 'For current job status use gpu_status'). Lacks prerequisites or conditional logic.

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/gpu-bridge/mcp-server'

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