tongji-ai-usage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
显示同济 AI 平台账户积分与用量。用 open_tongji_panel 打开交互面板。数据涵盖账户全部客户端，不能归因单轮 WorkBuddy 会话。不要请求、输出或粘贴网站令牌；自动登录由本机浏览器助手完成。
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_tongji_panelB | 查看同济 AI 账户的套餐余额、今日积分消耗、实际 Token 用量和登录状态，并打开可交互面板。 |
| get_tongji_usageB | 读取同济 AI 积分和用量；force 请求刷新，后端仍有短暂防重复缓存。 |
| tongji_loginA | 面板专用：配对浏览器助手、立即续期、启用或停用自动更新。不会返回网站令牌。 |
| tongji_check_updateA | 检查本插件 GitHub 仓库的正式版本，仅提示更新，不下载或执行软件。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 同济 AI 积分面板 | |
| 同济 AI 用量 · today | 面板自动刷新使用的账户用量与安全登录状态。没有网站令牌。 |
| 同济 AI 用量 · yesterday | 面板自动刷新使用的账户用量与安全登录状态。没有网站令牌。 |
| 同济 AI 用量 · 7d | 面板自动刷新使用的账户用量与安全登录状态。没有网站令牌。 |
TDQS
Scored across 4 tools
open_tongji_panel and get_tongji_usage both surface balance/credit/token data, so the boundary between 'show me data in a panel' and 'read usage data' is fuzzy. tongji_login is distinct but bundles three unrelated actions (pairing, renewal, auto-update toggle), which muddies its purpose. Descriptions do help distinguish the panel-opening intent.
Three different patterns appear: verb_tongji_noun (open_tongji_panel, get_tongji_usage), tongji_noun (tongji_login), and tongji_verb_noun (tongji_check_update). The tongji_ prefix is consistent and readable, but verb placement varies and tongji_login lacks a verb entirely.
Four tools is on the lean side for a usage-monitoring plugin but each maps to a plausible need: view, read, authenticate, and check for updates. No bloat, though it's close to feeling thin.
The core lifecycle (read usage, open panel, log in/pair, check for updates) is covered with no obvious dead ends. Minor gaps exist, such as no explicit logout/unpair or configuration of refresh behavior, but agents can work around these.