Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_group_member_stats

Retrieve member statistics for a Yuque group to analyze participation and manage team collaboration within the knowledge base.

Instructions

Get member statistics for a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.

Implementation Reference

  • src/tools.js:465-465 (handler)
    The implementation of the 'yuque_group_member_stats' tool handler.
    yuque_group_member_stats: async (args, client) => jsonText(await client.getGroupMemberStats(args.login)),
  • src/tools.js:394-404 (schema)
    The registration and input schema definition for the 'yuque_group_member_stats' tool.
    {
  name: "yuque_group_member_stats",
  description: "Get member statistics for a group.",
  inputSchema: {
    type: "object",
    properties: {
      login: schemaProperty("string", "Group login.")
    },
    required: ["login"]
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. States 'Get' implying read-only but does not disclose what statistics are returned (counts? activity metrics?), rate limits, or whether data is real-time versus cached. Missing behavioral context for a statistics endpoint.

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?

Single sentence, front-loaded with verb. Appropriate length for the information conveyed, though arguably under-sized for the complexity of behavioral disclosure needed. No wasted words.

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?

Adequate for low complexity (1 param, no nesting) but clear gaps remain. With no output schema, description should indicate what statistical data is returned to help agents select over alternatives like list_group_members.

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 has 100% coverage with 'Group login' described. Description mentions 'for a group' aligning with the login parameter but adds no syntax details, format examples, or where to obtain the login value. Baseline 3 appropriate since schema carries full load.

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?

Clear verb ('Get') and resource ('member statistics') with scope ('for a group'). Distinguishes from siblings like yuque_group_stats (general stats) and yuque_list_group_members (listing vs statistics), though could specify what statistics are returned.

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 versus yuque_list_group_members or other sibling tools. No mention of prerequisites like group membership requirements or when statistics are available versus raw member lists.

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/MichealJou/yuque-mcp-plus'

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