Skip to main content
Glama

account

Use this for any question about whether this API key works, how much wallet balance is left, remaining free catalog or identify quota, or how many free trial reports remain. The response names the key (name and prefix) so you can tell keys apart. An invalid key is rejected and is not charged. Free, limited to 120 per minute.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and largely meets it: it states that invalid keys are rejected and not charged (an important non-obvious side effect), sets a rate limit of 120 requests per minute, notes the call is free, and explains that the response identifies the key by name and prefix. It does not describe authentication failure modes or what a charge event looks like beyond validity, keeping it just short of full transparency.

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?

Four short sentences, front-loaded with the primary use case, then response identification, then failure/charge behavior, then rate limit. Every sentence adds a distinct fact; only the closing 'Free, limited to 120 per minute' is slightly clipped in style.

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?

For a zero-parameter read-only status check with an output schema present, the description covers use cases, key identification, invalid-key behavior, and rate limits — everything an agent needs before calling. Return-value detail is correctly delegated to the output schema.

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, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies for a zero-parameter tool.

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 resource precisely by enumerating the exact questions it answers: API key validity, wallet balance, remaining free catalog/identify quota, and free trial reports. An agent can tell this is the account/quota-status tool rather than a card or pricing tool, though the verb phrasing ('use this for any question about') is meta rather than a direct 'returns account status' statement.

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 an unusually explicit trigger list ('whether this API key works', 'how much wallet balance is left', 'how many free trial reports remain'), which maps directly onto the situations where an agent should call it. There are no stated exclusions or named alternatives, but for a zero-parameter status tool no alternative is needed, so the gap is minor.

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