mcp-user-system
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUS_BASE_URL | Yes | The base URL of the token-user-system API | |
| TUS_ACCESS_TOKEN | Yes | The access token for authentication |
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 |
|---|---|
| wallet_balanceA | Get account wallet overview (balance, usable balance, voucher, credit limit, pending amount) |
| wallet_trendA | Get consumption trend for a given number of days |
| wallet_transactionsC | List wallet transaction records with optional filters |
| wallet_couponsB | List my cash coupons |
| wallet_corporate_infoA | Get corporate transfer bank account info for recharge |
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 5 tools
Each tool targets a distinct wallet aspect: balance overview, corporate recharge info, coupons, transaction history, and consumption trend. No overlap.
All tools follow the consistent pattern 'wallet_<noun>' (e.g., wallet_balance, wallet_transactions). Perfectly uniform.
5 tools is well-scoped for a wallet subsystem, covering essential operations without bloat.
Covers core wallet needs but lacks direct recharge/deposit or withdrawal tools, though corporate info hints at external recharge.