Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_group_doc_stats

Retrieve document statistics for a group in the Yuque knowledge base to analyze content distribution and usage patterns.

Instructions

Get document statistics for a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.

Implementation Reference

  • src/tools.js:467-467 (handler)
    The handler function for the `yuque_group_doc_stats` tool.
    yuque_group_doc_stats: async (args, client) => jsonText(await client.getGroupDocStats(args.login))
  • src/tools.js:416-426 (schema)
    The tool registration and schema definition for `yuque_group_doc_stats`.
    {
  name: "yuque_group_doc_stats",
  description: "Get document 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 full burden but reveals only that this is a read operation. It omits what specific statistics are returned (counts, views, etc.), error handling for invalid groups, rate limits, or authentication requirements.

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 brief at six words with no redundancy. While efficient, the extreme brevity may be underspecified given the lack of behavioral annotations or output schema, though this reflects completeness rather than structural issues.

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?

Despite having only one parameter, the tool lacks critical context: no output schema is provided, no annotations indicate destructive/read-only status, and the description fails to clarify the return data structure or distinguish from related group statistics endpoints.

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 coverage is 100% (single parameter with description 'Group login'), establishing baseline 3. The description mentions 'for a group' which aligns with the parameter but adds no additional semantic context about login format, validation rules, or examples beyond the schema definition.

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?

States specific verb (Get) and resource (document statistics for a group), but fails to distinguish from siblings like 'yuque_group_stats' or 'yuque_group_book_stats', leaving ambiguity about when to select this specific endpoint versus broader group statistics.

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?

Contains no guidance on when to use this tool versus alternatives (e.g., yuque_group_stats), prerequisites for the group login parameter, or conditions where this should be preferred over repository-level document queries.

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