Skip to main content
Glama
Sign In
yuque-mcp

yuque-mcp

by Lorwy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

yuque_get_doc_version

Retrieve details of a specific historical version of a document using its version ID.

Instructions

获取文档历史版本详情

权限要求: read 参数:

  • id: 版本 ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "yuque_get_doc_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only discloses the read permission requirement, but lacks details on rate limits, idempotency, or other behavioral traits beyond the obvious read operation.

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?

The description is very short and front-loaded, with clear sections for permission and parameter. It is concise but could optionally include more detail without becoming verbose.

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?

With only one parameter and an output schema present, the tool is simple. The description covers the basic purpose and parameter, but lacks usage guidelines and behavioral context, making it adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds only a minimal label for the 'id' parameter ('版本 ID'), without example, format, or additional context. This provides some meaning but insufficiently compensates for the lack of schema descriptions.

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

Purpose5/5

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

The description clearly states the tool retrieves details of a document version ('获取文档历史版本详情'), using a specific verb and resource. It distinguishes from sibling 'yuque_get_doc_versions' which likely lists versions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions a permission requirement ('权限要求: read'), providing some context, but does not explicitly state when to use this tool versus alternatives like yuque_get_doc_versions or other siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools