Skip to main content
Glama

check_balance

Monitor API quota usage and verify tier status for NWO Robotics server operations.

Instructions

Check API quota usage and tier status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implementation of the checkBalance handler.
    async checkBalance() {
      const response = await axios.get(
        `${API_BASE}/api-agent-balance.php`,
        {
          headers: {
            'X-API-Key': API_KEY,
            'X-Agent-ID': AGENT_ID,
          },
        }
      );
      
      const data = response.data;
      return {
        content: [
          {
            type: 'text',
            text: `Tier: ${data.agent.tier}\n` +
                  `Quota Used: ${data.quota.used_this_month}\n` +
                  `Remaining: ${data.quota.remaining}\n` +
                  `Expires: ${data.subscription.expires_at || 'N/A'}`,
          },
        ],
      };
    }
  • server.js:116-122 (registration)
    Registration of the check_balance tool in ListToolsRequestSchema.
      name: 'check_balance',
      description: 'Check API quota usage and tier status',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'checking' API quota usage and tier status, which implies a read-only operation, but doesn't specify permissions, rate limits, or response format, leaving gaps in behavioral understanding.

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, efficient sentence that directly states the tool's purpose with zero waste. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks details on behavioral traits or usage context, making it just sufficient for a simple read operation.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a high baseline score.

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?

The description clearly states the tool's purpose with specific verbs ('check') and resources ('API quota usage and tier status'), making it easy to understand what the tool does. However, it doesn't differentiate from sibling tools, which are unrelated to API quota management (e.g., detect_objects, execute_robot_task), so it doesn't fully distinguish itself in context.

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 guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, timing, or comparisons with other tools, leaving the agent without explicit usage instructions.

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/RedCiprianPater/mcp-server-robotics'

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