Skip to main content
Glama

查账户 / Account

account
Read-only

查余额,以及当前这把 Key 已经花了多少。Balance, and what this key has spent.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the scope of returned data, namely balance plus key-level spend, but says nothing about authentication requirements, currency or units, staleness of the data, or formatting.

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 very short sentences, front-loaded with the primary data point, namely balance, before the secondary one, namely spend. The bilingual restatement of identical content is redundant for a single-language reader, though it serves a bilingual audience.

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?

The tool is simple and zero-parameter, and the description states both what it returns and its read-only nature is already covered by annotations, so there is no output schema gap. Minor omissions, such as units, refresh behavior, and whether spend is cumulative or per-period, keep it from a 5.

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?

There are zero parameters, so the baseline is 4. The description introduces no parameter concepts. The agent needs nothing from the description to form a valid call, because the empty schema is complete.

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 two specific pieces of data the tool returns: the account balance and how much the current API key has spent. That is a concrete verb+resource statement that distinguishes it from the sibling tools call, describe, and find, which are clearly different resources. It stops short of a 5 because it does not explicitly name or rule out those siblings.

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 it should call this when it needs balance or spend data. There is no explicit statement of when to use it, when not to, or which alternative to pick, although the sibling set offers no obvious substitute for account-level data.

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