Skip to main content
Glama
Vaquill-AI/vaquill-mcp

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Credit Balance

get_credit_balance
Read-only

Checks the spendable credits remaining for an API key using live billing buckets, enabling pre-flight balance checks and low-balance alerts.

Instructions

The credits this API key can spend now, calculated from live credit buckets under the same expiry rules used for billing. Use for pre-flight checks or low-balance alerts. creditsRemaining is a spendable balance, not a cached estimate. Any valid API key works without a particular scope, and normal rate limits still apply.

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": "get_credit_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: it discloses that the value is computed live from credit buckets rather than cached, that billing expiry rules apply, and that any valid API key works without a specific scope while normal rate limits still apply. Those are exactly the operational facts an agent needs before calling a quota-sensitive endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the definition, then use cases, then caveats — a sensible order with no filler. Minor deductions for a trailing space and for introducing the output field creditsRemaining before the reader knows the response shape.

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?

With an output schema present, return values need not be described; the description supplies scope, computation basis, use cases, auth expectations, and rate-limit behavior. Nothing needed to call a zero-param tool correctly is missing.

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, so there is nothing for the description to disambiguate in the schema; the baseline is 4. It also clarifies the meaning of the creditsRemaining output field as a spendable (non-cached) balance, which is bonus value.

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 resource (credits for this API key) and a precise computation basis (live credit buckets under the same expiry rules used for billing). An agent can immediately tell this apart from the legal-data siblings, which have nothing to do with billing.

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 concrete usage contexts: pre-flight checks and low-balance alerts. It does not name exclusions or alternatives, but there are no plausible sibling alternatives for balance lookups, so the guidance is effectively complete.

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