Skip to main content
Glama

Check credit balance

check_balance
Read-onlyIdempotent

Check the remaining Importly credit balance for the configured API key to diagnose failed jobs caused by insufficient credits or verify funds before large imports and transcriptions.

Instructions

Check the remaining Importly credit balance for the configured API key. Use this to diagnose failed jobs (insufficient credits) or as a pre-flight check before large imports/transcriptions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds useful context beyond that: the balance is tied to the configured API key (explaining the zero-parameter design) and the value is meaningful as a gating signal for credit-exhaustion failures. It does not describe the shape or units of the returned balance, which is the main remaining gap.

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 sentences, zero filler, with the identity of the resource front-loaded and the usage conditions following. Every clause carries information an agent needs.

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 trivial zero-parameter read with full annotation coverage, the description supplies purpose, scope and usage triggers. Without an output schema, a brief note on what the balance response contains (e.g., remaining credits vs. any threshold) would close the last gap.

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 takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The mention of the 'configured API key' usefully clarifies why no key argument is needed.

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?

States a specific verb and resource ('Check the remaining Importly credit balance') plus the scope ('for the configured API key'). The resource is unambiguous and cannot be confused with siblings like check_import or check_transcription, which report on job state rather than account credits.

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?

Gives two concrete when-to-use conditions: diagnosing failed jobs caused by insufficient credits, and as a pre-flight check before large imports/transcriptions. It does not state any when-not condition or name an alternative tool, so it falls just short of the top mark.

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