Skip to main content
Glama
Sign In
yuketang-mcp

yuketang-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

课件幻灯片

ykt_slides

Retrieve every page of a Yuketang slide presentation with page numbers and directly downloadable image URLs, so AI assistants can browse courseware without handling cookies or authentication.

Instructions

获取一份课件的全部页面。返回页码与图片地址；图片可直接 HTTP 下载，无需 Cookie 或鉴权参数。题目字段通常为 null（课后不返回题目内容）。

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": {
      "presentationId": "<presentationId>",
      "lessonId": "<lessonId>"
    },
    "name": "ykt_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNostandard
lessonIdYes所属课时 ID
withProblemNo是否附带题目字段（若存在）
presentationIdYes课件 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are present, so the description carries the full disclosure burden. It usefully adds that image URLs can be downloaded without Cookie or auth and that the problem field is usually null after class, but omits permission requirements, error behavior, pagination, and read-only status for the API call itself.

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?

Three concise sentences front-load the purpose, then cover return format and a caveat. The problem-field caveat could be better integrated, but overall it is efficient with little waste.

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?

No output schema and no annotations mean the description should be more self-sufficient. It explains the return shape and image auth well, but leaves region behavior, empty results, and error handling unaddressed for a 4-parameter retrieval tool.

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 75%, with three of four parameters described; region lacks a description but has an enum. The description does not directly map to presentationId, lessonId, region, or withProblem, so it does not compensate for the remaining regional parameter gap.

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?

States a specific verb and resource: '获取一份课件的全部页面' (get all pages of a courseware). It also specifies the return content (page numbers and image URLs). It does not explicitly contrast with siblings such as ykt_mind_map or ykt_lesson, so sibling differentiation relies on the name.

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 explicit when-to-use guidance, prerequisites, or alternatives are provided. The description implies it retrieves slides but leaves tool selection entirely to inference.

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