Skip to main content
Glama

yuque_group_stats

Retrieve comprehensive statistics for a Yuque knowledge base group to analyze content metrics and group activity.

Instructions

Get overall statistics for a group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loginYesGroup login.

Implementation Reference

  • The handler function for the `yuque_group_stats` tool.
    yuque_group_stats: async (args, client) => jsonText(await client.getGroupStats(args.login)),
  • The schema definition for the `yuque_group_stats` tool.
    {
      name: "yuque_group_stats",
      description: "Get overall statistics for a group.",
      inputSchema: {
        type: "object",
        properties: {
          login: schemaProperty("string", "Group login.")
        },
        required: ["login"]
      }
    },
Behavior2/5

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

No annotations provided, so the description carries full disclosure burden. It fails to specify what metrics are returned, whether the operation is read-only, or any rate limiting concerns. Beyond the implicit 'Get', no behavioral traits are disclosed.

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

Conciseness3/5

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

Single sentence with no redundancy, but brevity crosses into under-specification. Lacks front-loaded differentiators or scope definitions that would help distinguish from sibling tools.

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?

Given three specific sibling statistics tools and no output schema or annotations, the description should clarify what statistics 'overall' includes. It fails to compensate for missing structured data or explain the relationship to specific statistic variants.

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% description coverage for the single 'login' parameter ('Group login.'). The main description adds minimal semantic value beyond the schema, merely confirming this relates to a 'group'. Baseline 3 is appropriate given complete schema coverage.

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?

The description states a clear verb ('Get') and resource ('overall statistics for a group'), but critically fails to distinguish from siblings yuque_group_book_stats, yuque_group_doc_stats, and yuque_group_member_stats. It does not clarify what 'overall' encompasses versus these specific variants.

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 tool versus the specific group statistics siblings (book/doc/member stats). No mention of prerequisites, required permissions, or alternatives.

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