Skip to main content
Glama
MichealJou

yuque-mcp-plus

by MichealJou
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

yuque_get_doc_version

Retrieve a specific version of a document from the Yuque knowledge base by providing its version ID. This tool helps access historical document revisions within the enhanced Yuque MCP server for content management.

Instructions

Get a specific document version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionIdYesYuque version ID.

Implementation Reference

  • src/tools.js:457-457 (handler)
    Handler for yuque_get_doc_version tool.
    yuque_get_doc_version: async (args, client) => jsonText(await client.getDocVersion(args.versionId)),
  • src/tools.js:336-346 (schema)
    Schema definition for yuque_get_doc_version tool.
    {
  name: "yuque_get_doc_version",
  description: "Get a specific document version.",
  inputSchema: {
    type: "object",
    properties: {
      versionId: schemaProperty("number", "Yuque version ID.")
    },
    required: ["versionId"]
  }
},

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. While 'Get' implies read-only, it does not explicitly confirm safe/non-destructive behavior, disclose what data structure is returned, or explain what constitutes a document 'version' in Yuque.

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 5 words with no wasted words and front-loaded action verb. However, extreme brevity comes at the expense of necessary context for a versioning tool.

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?

Insufficient for a version control operation. With no output schema or annotations, the description should explain that this retrieves historical content, what the version contains, or how it relates to the current document, but provides none of this.

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 versionId parameter. The description adds no semantic information about the parameter, but baseline 3 applies per scoring rules for high schema coverage.

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 'document version', with 'specific' distinguishing it from sibling yuque_list_doc_versions. However, it fails to clarify the critical distinction from yuque_get_doc (historical version vs current document).

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 tool versus siblings like yuque_get_doc or yuque_list_doc_versions. Missing crucial prerequisite: that versionId must typically be obtained from yuque_list_doc_versions first.

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