maxtoken
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAXTOKEN_CONFIG | No | Path to the JSON config file containing your accounts (same as the --config command-line option). Defaults to ./tokens.json if not set. | ./tokens.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_balanceA | 查询 GLM 与 Kimi Coding Plan 账号的实时 Token/积分余额,包含 5小时滚动窗口及周(7d)/月(30d)周期的已用额度、剩余比例与重置时间。 |
| get_utilization_statsC | 统计 GLM 与 Kimi Coding Plan 的使用量与利用率指标,包含窗口时间流逝比、消耗速率比(Burn Rate)、预计重置时最终利用率及额度浪费比例。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have mostly distinct purposes: one focuses on utilization/burn-rate analytics, while the other focuses on real-time balance and quota status. However, both report used quota, remaining ratio, and reset timing, so an agent could occasionally confuse which tool to use for quota-related questions.
Both names follow a verb_noun pattern and are readable, but they use different verbs (get_ vs query_) for similar read operations. This is a minor inconsistency rather than a serious problem.
Two tools is thin for a monitoring server, even if the domain is narrow. The surface feels minimal and may require agents to infer too much from only two operations.
The tools cover the core monitoring needs: utilization metrics and real-time balance/quota status across GLM and Kimi plans. Minor gaps remain, such as account listing or historical trend queries, but core workflows are covered.