io.github.AceDataCloud/mcp-glm
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEDATACLOUD_API_TOKEN | Yes | Your AceDataCloud API token. Get from https://platform.acedata.cloud |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glm_chat_completionsA | Create a GLM chat completion using the AceDataCloud GLM API. |
| glm_list_modelsA | List all available GLM models for the GLM API. |
| glm_get_usage_guideA | Get a comprehensive guide for using the GLM tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| glm_guide | Guide for choosing the right GLM tool and model for chat completion tasks. |
| glm_workflow_examples | Common workflow examples for GLM tasks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: usage guidance, chat completion generation, and model listing. There is no overlap or ambiguity between them, so an agent would never struggle to choose the right one.
All tool names use the same glm_ prefix and a consistent lower_snake_case style. The verb-noun pattern is uniform (get_usage_guide, chat_completions, list_models), making the set predictable and easy to navigate.
Three tools is well-scoped for a focused GLM chat completions server. Each tool earns its place, and the set feels neither bloated nor too thin.
The server covers the core lifecycle of chat completion: listing models and making completions, plus an onboarding guide. It lacks endpoints for embeddings or model-specific detail, but those are likely outside the intended scope.