Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_get_user

Retrieve the current authenticated user from the Yuque knowledge base platform to enable personalized content management and access control.

Instructions

Get the current Yuque user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.js:433-433 (handler)
    The handler implementation for the yuque_get_user tool.
    yuque_get_user: async (_args, client) => jsonText(await client.getUser()),
  • src/tools.js:92-95 (registration)
    The tool registration for yuque_get_user.
      name: "yuque_get_user",
  description: "Get the current Yuque user.",
  inputSchema: { type: "object", properties: {} }
},

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, yet description fails to disclose critical behavioral traits: authentication requirements needed for 'current' user resolution, what user attributes are returned, or error behavior when unauthenticated. Carries minimal behavioral burden.

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 (5 words), but no wasted language. Front-loaded action verb. However, given lack of supporting metadata (annotations/output schema), appropriate length would include slightly more context.

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 a simple zero-parameter read operation, but gaps remain: no mention of return structure (user profile fields) despite absent output schema, and silent on auth/session requirements which are critical for 'current' user semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters present; per scoring rules, baseline is 4. Description correctly implies no inputs are needed to retrieve the current user context.

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 specific resource ('current Yuque user'). Effectively distinguishes from sibling tools that operate on repos, docs, and groups by targeting the authenticated user entity.

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?

Provides no guidance on when to invoke (e.g., to check authentication status or retrieve user ID for subsequent calls) nor prerequisites (authentication requirements). No alternatives or exclusions mentioned.

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