Skip to main content
Glama
Sign In
yuketang-mcp

yuketang-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

课程班级详情

ykt_classroom

Retrieves detailed information for a specific Yuketang course classroom, including course name, teacher, school ID, and class start and end times. Use it to look up classroom metadata by classroom ID and optional region.

Instructions

某课程班级的详细信息：课程名、教师、学校 ID、班级起止时间。

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

Input Schema

NameRequiredDescriptionDefault
regionNostandard
classroomIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/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 disclosure burden, yet it never states that this is a read-only lookup, whether authentication or a session from ykt_login is required, or what happens if classroomId is invalid. The return-field list is the only behavioral content.

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 compact sentence with the resource front-loaded and no filler. It is efficient, though the brevity comes partly from omitting information rather than from disciplined editing.

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 no output schema and no annotations, the description should cover how to identify the classroom, what region does, and the read-only/auth context; it covers only a sample of return fields. An agent can guess how to call it, but only by guessing.

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%, and the description compensates for none of it: classroomId's expected format is unstated, and the region parameter with its four enum values (standard/hetang/changjiang/huanghe) is not mentioned at all. "学校 ID" in the description is a return field, not a parameter, so it adds no parameter meaning.

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 the resource (a course classroom) and enumerates the concrete fields returned (course name, teacher, school ID, class start/end times), so the agent can tell this is a detail-lookup tool. The verb is only implied by "详细信息", and nothing distinguishes it from siblings such as ykt_courses or ykt_lesson.

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 instead of ykt_courses, ykt_lesson, or ykt_course_progress, nor any stated prerequisites. The agent must infer usage purely from the name and the field list.

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