Skip to main content
Glama

Your token balance

research_account_tokens
Read-onlyIdempotent

Free. Your balance, the grant that resets each period, purchased tokens that carry over, this period's spend by operation, and your recent charges. Every metered result already carries tokens_charged and tokens_remaining; call this when the user asks how many tokens are left or a call was refused for insufficient tokens.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
grantYesTokens granted every period (resets at the roll, use it or lose it)
recentNoYour last charges, newest first
balanceYesTokens you can spend right now: this period's grant left + purchased
period_endNoWhen the grant resets (null only for an open-ended promo)
period_startYes
grant_remainingNoThis period's grant still unspent; balance = grant_remaining + purchased_remaining
spent_this_periodYes
spent_by_operationNoThis period's spend per operation (search, facets, component, component.text...) — the whole period, not just the recent rows
purchased_remainingYesBought tokens carry across periods until spent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context, which it does: 'Free' tells the agent this call is not itself metered, and the failure-mode note about calls being refused for insufficient tokens explains a system behavior the agent can act on. It does not cover pagination or limits on recent charges, which are minor gaps against a read-only tool.

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, both front-loaded: 'Free.' establishes the cost implication immediately, then the payload is listed, then the trigger conditions. No filler or restatement of the tool name.

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 an output schema present, the description did not need to enumerate return contents, yet doing so still helps the agent decide whether a call will answer the user's question. Combined with the explicit invocation triggers, an agent has enough to call this correctly; only the redundancy with the output schema and the vagueness of 'recent charges' keep it just short of full marks.

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 at all, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly adds no parameter guidance, which is the right call for an empty schema.

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?

The description names a specific resource and enumerates exactly what it returns: balance, the per-period resetting grant, purchased tokens that carry over, this period's spend by operation, and recent charges. That scope is unmistakably distinct from the research_* content siblings, which operate on components, corpora, facets, and titles rather than account billing state.

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?

It gives concrete triggering conditions: the user asks how many tokens are left, or a call was refused for insufficient tokens. It also implies a when-not by noting that every metered result already carries tokens_charged and tokens_remaining, so a separate call is usually redundant — though this is stated indirectly rather than as an explicit exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources