yuketang-mcp

课时详情

ykt_lesson

Fetches lesson metadata and its courseware inventory by lesson ID, including all presentation IDs when a lesson contains multiple files.

Instructions

查询一次课堂的元信息与课件清单。presentationIds 是数组，一次课可能有多份课件。

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

Input Schema

Name	Required	Description	Default
`region`	No		standard
`lessonId`	Yes	课时 ID（来自活动列表的 coursewareId）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 29, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 查询 makes it clear this is a read-only lookup, and the note that one lesson can have multiple courseware pieces discloses the shape of the result, but authorization requirements and the meaning of the region selector are never explained.

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?

Two short sentences with no filler, and the core purpose is front-loaded. The second sentence is the only slightly odd piece, since presentationIds is not an input parameter.

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?

There is no output schema, so spelling out that the result includes metadata and a courseware list with a possibly multi-element presentationIds is genuinely useful. Still missing is any explanation of the region enum's effect on the response, which leaves a real ambiguity for a tool with no annotations.

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 coverage is only 50%: lessonId is documented, but region has no schema description despite being a four-value enum, and the description never mentions region at all. The presentationIds sentence describes an output field, not an input parameter, so the description does not compensate for the coverage 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?

The description names a specific verb and resource (查询一次课堂的元信息与课件清单), so an agent can tell this is a per-lesson detail lookup rather than a list tool like ykt_activities or a slide fetcher like ykt_slides. Minor wording drift between '课堂' and the title '课时' slightly blurs whether it returns classroom or lesson data.

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?

There is no guidance on when to call this versus ykt_activities, ykt_slides, or ykt_lesson_summary. The only hint, that lessonId comes from an activity list's coursewareId, is already stated in the schema, so the description adds no routing information.

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

Deploy Server