Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

打开浏览器进行 PingCode 登录(支持飞书等第三方登录)。登录成功后凭证会自动保存。

logoutA

退出 PingCode 登录,清除本地保存的凭证。

check_authB

检查当前 PingCode 登录状态。

get_work_itemB

通过 PingCode 工作项编号获取详情。支持格式:#12345、12345、LFY-123 等。

get_release_itemsC

获取某个发布版本关联的缺陷和需求列表。

search_work_itemsC

搜索 PingCode 工作项。

list_releasesC

列出项目的所有发布版本。用户可以通过此工具查看版本名称和对应的 ID。

list_projectsB

列出用户可访问的所有项目。返回项目标识和名称列表。

update_work_item_stateC

更新工作项(缺陷/需求/任务)的状态。通过状态名称指定目标状态。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes, such as authentication (check_auth, login, logout), project/release management (list_projects, list_releases), and work item operations (get_work_item, search_work_items, update_work_item_state). However, get_release_items overlaps slightly with list_releases in dealing with releases, but its focus on associated items provides enough differentiation to avoid major confusion.

Naming Consistency4/5

The tools follow a consistent verb_noun pattern throughout, such as check_auth, get_work_item, and list_projects, which enhances readability. There are minor deviations like update_work_item_state using 'state' instead of a more specific noun, but overall the naming is predictable and well-structured.

Tool Count5/5

With 9 tools, the server is well-scoped for managing PingCode projects, releases, and work items. Each tool serves a clear purpose, such as authentication, listing, searching, and updating, without redundancy, making the count appropriate for the domain's core workflows.

Completeness4/5

The tool set covers key operations like authentication, project/release listing, and work item retrieval/search/updates, providing a solid foundation. A minor gap exists in the lack of tools for creating or deleting work items or releases, which agents might need to work around, but core lifecycle management is largely supported.

Maintenance

ActivityInactive
ResponsivenessNo issues