d1jiema-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| D1JIEMA_BASE_URL | No | Optional base URL for the D1Jiema API. The default API base address is https://api.d1jiema.com/zc/data.php. | |
| D1JIEMA_API_TOKEN | Yes | D1Jiema API Token, created from the API Token creation page. Required in environments without a graphical interface. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"openai/settings": {
"readTool": "d1jiema_settings_read",
"updateTool": "d1jiema_settings_update"
}
} |
| experimental | {
"openai/settings": {
"readTool": "d1jiema_settings_read",
"updateTool": "d1jiema_settings_update"
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| d1jiema_settings_readA | Read D1Jiema settings. The API token is always masked. |
| d1jiema_settings_updateC | Save the D1Jiema token from the settings page. |
| d1jiema_setup_localA | Launch a one-shot localhost form for entering the D1Jiema API token. The form closes after saving. |
| d1jiema_loginC | Open the local D1Jiema token configuration flow. D1Jiema creates API tokens from its web personal center. |
| d1jiema_balanceB | Read the D1Jiema account balance using leftAmount. |
| d1jiema_get_phoneC | Get a D1Jiema phone number. Optional keyword, exact phone, province, and card type filters are passed through. |
| d1jiema_get_smsC | Fetch the SMS containing the required keyword for a phone number. |
| d1jiema_releaseB | Release a D1Jiema phone. This changes account state; set confirm=true explicitly. |
| d1jiema_blockA | Block a D1Jiema phone. This is irreversible account state; set confirm=true explicitly. |
| d1jiema_send_smsB | Send an SMS through D1Jiema. Use only for an explicitly authorized recipient and content; set confirm=true. |
| d1jiema_historyA | Read the last 24 hours of D1Jiema history. The API allows at most one call per minute; set confirm_rate_limit=true. |
| d1jiema_requestB | Call any documented D1Jiema GET operation by code. Write-like codes require confirm=true. |
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 12 tools
The set includes four token/config tools (settings_read, settings_update, setup_local, login) whose boundaries are fuzzy—especially setup_local vs login, both of which open a local token flow. The generic d1jiema_request also overlaps with all specific read tools, though it is clearly marked as a catch-all.
All tools share the d1jiema_ prefix and snake_case, but the verb/noun pattern is inconsistent: some use verb_noun (get_phone, send_sms), some noun_verb (settings_read), and others are bare verbs or nouns (login, balance, history). The style is readable but not predictable.
12 tools is within a reasonable range for an SMS/phone service. However, four tools for token configuration alone feels slightly over-provisioned, keeping it from a perfect score.
Core lifecycle operations—phone acquisition, SMS retrieval, release, block, send, balance, history—are covered, and the generic request tool extends read coverage to any documented GET operation. Minor gaps remain (e.g., explicit phone status check or token deletion), but agents have workarounds.