Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GLM_MODELNoModel to use. The Coding Plan supports glm-5.3 and glm-5.3-flash.glm-5.3
GLM_API_KEYYesYour Coding Plan API key. Required.
GLM_BASE_URLNoCoding Plan address. Mainland-China accounts should use https://open.bigmodel.cn/api/anthropichttps://api.z.ai/api/anthropic
GLM_MAX_TOKENSNoOutput limit per round (this project's choice, not an official cap)32768
GLM_MAX_RETRIESNoRetries on 429, 5xx and concurrency errors4
GLM_MAX_CONCURRENTNoRequests sent to GLM at the same time1
GLM_AGENT_MAX_ITERSNoMaximum rounds per task30
GLM_STALL_TIMEOUT_MSNoHow long to wait in silence before retrying120000
GLM_AGENT_BASH_TIMEOUT_MSNoTime limit for one shell command120000

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
glm_agentA

Delegate a self-contained coding task to a GLM sub-agent (use when the user asks for GLM or glm_agent, or wants to save Claude tokens). GLM works inside workdir with its own read/write/edit/list/bash tools and returns a summary plus the list of changed files. Give a complete task description (goal, constraints, how to verify); GLM does not see this conversation. workdir must be an absolute path. File tools cannot leave workdir; bash is not sandboxed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool is exposed, so there is zero risk of selecting the wrong tool. Its purpose—delegating a self-contained coding task to a GLM sub-agent—is clearly stated and distinct.

Naming Consistency5/5

The single tool uses snake_case (`glm_agent`), which is a standard, predictable convention. With only one tool, consistency is trivially satisfied.

Tool Count4/5

One tool is slightly below the typical 3–15 range, but the server is a focused, single-purpose delegation wrapper. The tool is substantial rather than trivial, so the count is reasonable though thin.

Completeness4/5

The tool covers the core delegation lifecycle: accept a task, run it in a workdir, return summary and changed files. However, it lacks follow-up operations like status, cancellation, or session continuation, which could be useful for long tasks.

Maintenance

ActivityMaintained
ResponsivenessNo issues