Skip to main content
Glama
Sign In
yuketang-mcp

yuketang-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

课堂小结

ykt_lesson_summary

Retrieve a lesson overview with title, courseware list, and check-in status to understand the structure of a class session.

Instructions

课堂概览：课件清单、签到状态、课堂标题。用于快速了解一次课的构成。

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNostandard
lessonIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. To its credit it discloses the return payload shape (courseware list, check-in status, class title), which is the single most useful behavioral fact here since there is no output schema. It says nothing about whether any state is mutated (the name suggests a read-only aggregate), nor about permissions or whether the check-in status is per-student or class-level.

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 clauses with no filler, and the content list is front-loaded ahead of the usage note. Slightly tight to a fault — the space saved on brevity would have been better spent on the region 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?

With no output schema, the description correctly spends its words on what the tool returns, which is the right instinct. But for a 2-parameter tool with 0% schema coverage and no annotations, it omits both parameter meaning and any differentiation from overlapping siblings, leaving real gaps an agent must resolve by trial.

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%, so both parameters — including the required lessonId and the region enum (standard/hetang/changjiang/huanghe) — are undocumented everywhere. The description never mentions either parameter, leaving the agent to guess what region means (regional deployment variant?) and where to obtain a lessonId.

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

Purpose3/5

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

The description frames the tool as a 'classroom overview' and enumerates the contents it surfaces (courseware list, check-in status, class title), which conveys the resource. However, it uses a noun phrase rather than a clear verb, and it never distinguishes this from the closely-named sibling ykt_lesson or from ykt_slides/ykt_classroom, which plausibly overlap. The purpose is understandable but not sharply differentiated.

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?

'用于快速了解一次课的构成' implies a use case (a quick orientation before deeper work), so usage is inferable. But there is no explicit when-to-use versus when-not, and no pointer to the obvious alternatives (ykt_lesson, ykt_slides) that an agent would need to choose correctly among 15 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