yuketang-mcp

讨论区与公告

ykt_discussion

Fetch course announcements or discussion topic lists from a Yuketang classroom by classroom ID, with pagination and regional deployment options.

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": {
      "classroomId": "<classroomId>"
    },
    "name": "ykt_discussion"
  }
}

Input Schema

Name	Required	Default
`kind`	No	announcements
`limit`	No
`offset`	No
`region`	No	standard
`classroomId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 29, 2026

TDQS

C2.9/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 the full behavioral burden. '读取' implies a read-only operation, but it says nothing about permissions, pagination behavior, result ordering, or what happens with the default kind/region. For a five-parameter tool with zero annotation coverage this is a substantial gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity leaves the tool under-explained rather than over-explained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, 0% schema description coverage, no annotations, and no output schema, the description should explain at least the required classroomId, pagination, and the region scope. It covers only the resource type, leaving an agent to guess at most of the call contract.

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 the description must compensate, yet it only implicitly covers the kind choice (announcements vs topics). It says nothing about classroomId being required, what limit/offset do, or what the region enum (standard/hetang/changjiang/huanghe) means for results.

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 (读取/list) and two concrete resources (课程公告 announcements, 讨论区帖子 discussion posts), which matches the tool name and title. It is clear what the tool returns, though it does not explicitly differentiate itself from siblings like ykt_activities or ykt_lesson_summary, which could also surface course content.

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 phrase '公告或讨论区帖子' implies the two modes of use, but there is no statement of when to choose announcements vs topics, no prerequisites (e.g., must be enrolled / logged in), and no mention of alternatives. Usage must be inferred from the kind enum rather than from the text.

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

Deploy Server