Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_group_book_stats

Retrieve repository statistics for groups to analyze content usage and performance metrics within the Yuque knowledge base platform.

Instructions

Get repository statistics for a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.

Implementation Reference

  • src/tools.js:466-466 (handler)
    The handler for 'yuque_group_book_stats' which calls client.getGroupBookStats.
    yuque_group_book_stats: async (args, client) => jsonText(await client.getGroupBookStats(args.login)),
  • src/tools.js:406-415 (schema)
    The schema definition for 'yuque_group_book_stats'.
      name: "yuque_group_book_stats",
  description: "Get repository statistics for a group.",
  inputSchema: {
    type: "object",
    properties: {
      login: schemaProperty("string", "Group login.")
    },
    required: ["login"]
  }
},

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but reveals nothing beyond the operation type. It omits what specific statistics are returned (count, views, size), whether the operation is read-only, or any permission requirements specific to group data access.

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?

Extremely concise at five words. While no words are wasted, the description is under-specified rather than efficiently informative. It front-loads the action but lacks supporting context that would justify its brevity.

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

Completeness2/5

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

Inadequate for a statistics retrieval tool with no output schema. The description fails to specify what statistical metrics are returned (document counts, view statistics, storage usage), leaving the LLM with no understanding of the tool's utility or return value structure.

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?

Input schema has 100% coverage ('Group login.') and the description mentions no parameters. While the schema adequately documents the single required field, the description adds no semantic value regarding what constitutes a group login or format constraints.

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

Purpose3/5

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

Provides a specific verb ('Get') and resource ('repository statistics for a group'), but fails to distinguish from siblings like 'yuque_group_stats' (general group stats) or clarify that 'book' in the name maps to 'repository' in the description. The terminology gap and lack of scope differentiation create ambiguity in a dense toolset.

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 provided on when to use this versus 'yuque_group_stats', 'yuque_get_repo', or other similar retrieval tools. Given the numerous sibling statistics and repository tools, the absence of selection criteria forces the LLM to guess based on naming conventions alone.

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