Skip to main content
Glama

Check Prepaid USDC Credit Balance & Free Query Status (Free)

get_credits_and_payment_info
Read-onlyIdempotent

Checks remaining free queries or prepaid credit balance and reports remaining call count for an optional Base USDC transaction hash.

Instructions

100% free utility tool with zero cost. Checks remaining free queries or optional prepaid credit balance and remaining call count for any Base USDC transaction hash (0x...).

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_credits_and_payment_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashNoOptional 66-character Base USDC transaction hash ("0x...") to verify on-chain and check remaining prepaid credit balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true. The description's main addition is the cost profile (free, zero cost) and that verification happens on-chain, which the annotations do not state. It says nothing about rate limits, latency, or failure behavior, so value beyond structured data is modest.

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?

Two sentences, front-loaded with the key free/cost fact. Slight redundancy between "100% free" and "zero cost", which are the same claim restated, but otherwise no waste.

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?

With no output schema, the description does name what is returned — remaining free queries, prepaid credit balance, remaining call count — which is what an agent needs. For a simple, read-only, single-optional-param tool this is close to complete; only failure/on-chain-verification edge cases are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is fully documented, so baseline is 3. The description reinforces the optionality and format ("0x...") already in the schema but adds little new meaning beyond that.

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 and resource: checks remaining free queries and prepaid credit balance (plus remaining call count) for a Base USDC transaction hash. The scope and the conditional/optional nature of the input are clear. It does not differentiate from siblings, but the siblings (alpha/token-security tools) are unrelated, so that matters little.

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?

"100% free utility tool with zero cost" and "optional" txHash imply this can be called freely and without an input, which is useful usage context. However, there is no explicit statement of when to call it (e.g., before a paid query) or when not to, so guidance remains implied rather than stated.

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