Skip to main content
Glama
AceDataCloud

io.github.AceDataCloud/mcp-glm

Official
by AceDataCloud

glm_chat_completions

Create chat completions using Zhipu GLM models through AceDataCloud API. Handles Chinese language understanding, generation, and reasoning. Send messages to get responses.

Instructions

Create a GLM chat completion using the AceDataCloud GLM API.

Sends messages to the specified GLM model and returns the generated response.
Supports all GLM models: glm-5.2, glm-5, glm-5-turbo, glm-5.1, glm-4.7, glm-4.6, glm-3-turbo.

Use this when:
- You need to chat with a Zhipu GLM model
- You need Chinese language understanding or generation
- You want to use GLM's reasoning capabilities

Returns:
    JSON response containing the chat completion result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoHow many chat completion choices to generate. Default 1.
seedNoRandom seed for deterministic sampling.
stopNoStop sequences where the API will stop generating tokens.
userNoEnd-user identifier for abuse monitoring.
audioNoParameters for audio output.
modelNoThe GLM model to use. Options: glm-5.2, glm-5, glm-5-turbo, glm-5.1, glm-4.7, glm-4.6, glm-3-turbo. Default is glm-5.2.glm-5.2
storeNoWhether to store the output of this request. Default False.
toolsNoList of tools the model may call.
top_pNoNucleus sampling probability mass. Default 1.
streamNoWhether to stream partial message deltas. Default False.
logprobsNoWhether to return log probabilities of output tokens. Default False.
messagesYesConversation messages. Each message is a dict with 'role' and 'content' keys. Required.
metadataNoKey-value pairs for storing additional information.
logit_biasNoModify the likelihood of specified tokens appearing in the completion.
max_tokensNoMaximum number of tokens to generate.
modalitiesNoOutput types to generate (e.g. ['text', 'audio']).
predictionNoStatic predicted output content for latency reduction.
temperatureNoSampling temperature between 0 and 2. Higher = more random. Default 1.
tool_choiceNoControls which tool is called. Can be 'none', 'auto', or a dict.
service_tierNoService tier: auto, default, flex, scale, priority. Default auto.
top_logprobsNoNumber of most likely tokens to return at each token position.
stream_optionsNoOptions for streaming response.
response_formatNoResponse format specification (e.g. {"type": "json_object"}).
presence_penaltyNoPresence penalty between -2.0 and 2.0. Positive values increase topic variety. Default 0.
reasoning_effortNoReasoning effort level: minimal, low, medium, high. Default medium.
frequency_penaltyNoFrequency penalty between -2.0 and 2.0. Positive values decrease repetition. Default 0.
web_search_optionsNoOptions for web search tool.
parallel_tool_callsNoEnable parallel function calling. Default True.
max_completion_tokensNoUpper bound for tokens that can be generated for a completion.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states that it sends messages and returns a JSON response, without mentioning side effects (e.g., token consumption/cost), authentication requirements, streaming behavior, or error conditions. This is insufficient for a complex API call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured clearly with an intro, usage bullets, and returns section. It is compact, but the model list duplicates the schema enum and could be trimmed. Still, no sentence is wasted overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Considering the tool's complexity (29 parameters), full schema coverage, and an output schema, the description provides adequate high-level guidance. It does not discuss nuances like streaming, tool calling, or error handling, but these are optional given the schema's richness. It is complete enough for selection but not for deep invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% parameter coverage with detailed descriptions, so the baseline is 3. The tool description adds no parameter-level details beyond repeating the model list from the schema, thus not exceeding the schema's contribution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: 'Create a GLM chat completion'. It explains what it does (sends messages, returns generated response) and is easily distinguished from sibling tools (glm_list_models, glm_get_usage_guide) by focusing on the core chat generation functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists when to use the tool via 'Use this when' scenarios: chatting with a Zhipu GLM model, Chinese language tasks, and reasoning capabilities. It does not mention when not to use it or explicitly name alternatives, but the context is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/GlmMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server