Skip to main content
Glama
Sign In
yuketang-mcp

yuketang-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

课堂笔记

ykt_notes

List classroom notes and retrieve a specific note's body by liveId; call without liveId first to get the catalog, then fetch the desired note content on demand.

Instructions

列出课堂笔记；提供 liveId 时返回该笔记的正文。先用不带 liveId 的调用拿目录，再按需取正文。

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

Input Schema

NameRequiredDescriptionDefault
liveIdNo省略则只返回目录
regionNostandard
lessonIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description must carry behavioral burden. It does disclose the important mode switch (index vs. body content), but says nothing about permissions, auth/login prerequisites, result size, or pagination for a notes listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight clauses covering purpose and the recommended call sequence. No filler, and the workflow hint is front-loaded.

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, so the description should say more about what the listing returns and what region changes. The mode split is covered, but an agent still lacks enough to call confidently with a non-default region.

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 only 33%, so the description must compensate and does for liveId (its omission means index-only). However lessonId is never explained and the region enum with four values is undocumented in both schema and description, leaving real ambiguity about regional variants.

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?

Specific verb+resource: "列出课堂笔记" plus a second mode "提供 liveId 时返回该笔记的正文". The dual listing/content behavior is stated precisely, though it never contrasts itself with adjacent tools like ykt_slides or ykt_lesson_summary.

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

Usage Guidelines4/5

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

Gives an explicit two-step calling sequence: call without liveId to get the index, then fetch content as needed. Clear usage context, but no when-not guidance or comparison to sibling tools.

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