Skip to main content
Glama
Sign In
PingCode MCP

PingCode MCP

by frontendRicky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List PingCode Team Members

pingcode_get_team_members

Get a paginated list of enterprise team members, filterable by keywords and up to 20 department IDs.

Instructions

查询企业成员列表（只读），支持关键字与部门 ID（≤20）过滤、分页。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pingcode_get_team_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNo按姓名/邮箱等关键字过滤企业成员。
pageSizeNo
pageIndexNo
departmentIdsNo部门 ID 列表，≤20，多个为「任一部门」。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description provides 'read-only' context, but does not disclose permission requirements, rate limits, or side effects. This is adequate for a simple list tool.

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

Conciseness5/5

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

A single, dense sentence efficiently conveys the tool's purpose, read-only nature, and key features (filtering, department ID limit, pagination). No superfluous content.

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?

The description covers input filtering and pagination but omits output details. Given no output schema, a brief note on the returned data structure would improve completeness.

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?

Schema description coverage is 50%; the description mentions filtering by keyword and department ID and pagination, adding some context beyond schema. However, pageSize and pageIndex lack descriptions in both schema and tool description.

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

Purpose4/5

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

The description clearly states the tool queries an enterprise member list and is read-only. It does not explicitly differentiate from sibling tools, but the purpose is distinct from work-item-related siblings.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_current_user or get_current_team. The description lacks context for optimal usage and exclusions.

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

Deploy Server

Other Tools