Skip to main content
Glama

account

Free. Credits left (they never expire), prices per call, the last calls and credit movements. Use it when the user asks about credits, balance, usage or cost.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description does useful work by stating the call is 'Free' and that credits never expire, both of which affect how an agent should interpret and act on the result. It does not explicitly confirm the operation is a read, nor describe response shape, currency/units, or history depth for 'last calls', leaving real behavioral gaps for an annotation-free tool.

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?

The cost-relevant fact 'Free' is front-loaded, followed by a compact enumeration of payload contents and one usage sentence. The middle sentence is telegraphic and fragmentary ('the last calls and credit movements'), but nothing is redundant.

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 zero parameters and no output schema, the description must convey the return value itself, and it enumerates the four data groups returned. Missing are details an agent might need to report results accurately, such as units of credit or how many 'last calls' are included, but overall it is sufficient for this simple tool.

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 there is no parameter meaning to add and the baseline is 4. The description correctly implies no filtering arguments are available.

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?

The description names the concrete contents returned: remaining credits, per-call prices, recent calls, and credit movements, which tells an agent this is the billing/usage resource rather than a brand, ad, or experiment tool. The verb is only implied (no 'returns'/'retrieves'), and the bare name 'account' carries no meaning on its own, so it falls short of a 5.

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 explicit trigger phrases: use when the user asks about credits, balance, usage, or cost. That is a clear usage condition; there are no stated exclusions or named alternatives, but the sibling list suggests no other tool covers billing, so none are needed.

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