Skip to main content
Glama

Credit usage

credits
Read-onlyIdempotent

Retrieve the authenticated account's credit usage and remaining balance to track consumption and available funds.

Instructions

Get the authenticated account's credit usage and remaining balance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile and closed-world scope are fully covered there. The description adds only that the data is scoped to the authenticated account, which is useful but minimal; it says nothing about freshness of the usage numbers or whether cost is a hard limit. With an output schema present, the return shape does not need explaining.

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?

A single sentence with the verb front-loaded and zero filler. Every word contributes: 'authenticated account' establishes scope, 'credit usage and remaining balance' names both returned quantities.

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 zero-parameter read with full annotation coverage and an output schema defining return values, the description is essentially sufficient. The only minor gap is that it does not steer the agent relative to nearby tools such as 'account' or 'estimate', which a slightly longer definition could address.

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 zero parameters, so the baseline is 4; the description correctly implies no input is needed to get account-wide usage. There is no parameter meaning to clarify and nothing misleading.

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?

Uses a specific verb (Get) plus a clear resource (credit usage and remaining balance) scoped to the authenticated account, so an agent knows exactly what it returns. It does not distinguish itself from the sibling 'account' tool, which could plausibly also surface billing/plan information, leaving mild overlap ambiguity.

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?

Usage is only implied: an agent can infer this is the tool to check balance or usage before running costly operations, but the description never says when to call it or what alternative to use. There is no explicit precondition or exclusion, and no mention of frequency or caching considerations.

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