Skip to main content
Glama
Sav1ouR520

xiaoya-teacher-mcp-server

by Sav1ouR520
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

create_code_question

Create a programming question with customizable title, description, test cases, and code answer. Configure language, memory, time limits, and answer settings for automated grading.

Instructions

创建编程题

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes试卷ID（通过 query_group_tasks 获取）
questionYes编程题。各字段说明： title_raw 题干富文本，建议分行写：题目说明 / 输入格式 / 输出格式 / 样例 description 解析或补充说明，不能放参考代码 program_setting 配置语言、code_answer 参考代码、in_cases 测试输入列表、内存/时间限制
need_parseNotrue 返回纯文本（plain），false 返回原始富文本结构（raw）
need_detailNo是否在返回中包含完整题目内容（选项、答案等），仅需确认成功时设为 false

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv1.5.2
    • changedInput schema / $defs / CodeQuestion / properties / title / description
      Previous value: -"题干纯文本（与 title_raw 二选一）。只在一两行的简单题目用；结构化题干（OJ、分小节）走 title_raw。"New value: +"题干纯文本（与 title_md/title_raw 三选一）。只在一两行的简单题目用。"
    • addedInput schema / $defs / CodeQuestion / properties / title_assets
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "题干 Markdown 引用的资源列表，仅与 title_md 一起使用。格式：[{\"id\":\"img_1\",\"type\":\"image\",\"name\":\"图.png\",\"file_path\":\"/abs/图.png\"}]；图片占位：![说明](asset://img_1)，附件占位：[附件名](asset://file_1)。",
+  "title": "Title Assets"
+}
    • addedInput schema / $defs / CodeQuestion / properties / title_md
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "题干 Markdown（与 title/title_raw 三选一）。工具会自动转为小雅 Draft.js 富文本；适合 AI 输出的分节题干、列表、代码块、样例输入输出；图片/附件用 asset://id 占位并配合 title_assets。",
+  "title": "Title Md"
+}
    • changedInput schema / $defs / CodeQuestion / properties / title_raw / description
      Previous value: -"题干富文本（Draft.js 格式），与 title 二选一，优先本字段。\n格式：{\"blocks\": [...], \"entityMap\": {}}，每行一个 block，空行 = text=\"\" 的 unstyled block。\nblock.type 常用：unstyled / header-one~six / code-block / ordered-list-item / unordered-list-item / blockquote。\ninlineStyleRanges.style 常用：BOLD / ITALIC / UNDERLINE / CODE / lineThrough / color-red / backgroundColor-#ffff02 / fontSize-20。\noffset/length 以 UTF-16 单位计数（中文一字 1 单位）。\n美化要点：小标题【XX】整段 BOLD、小节间留空行、样例用 code-block、关键词用 CODE 或 color-blue；\n完整支持矩阵见 xiaoya-teacher-skill/references/title_rich_text.md。"New value: +"题干富文本（Draft.js 格式），与 title/title_md 三选一，优先本字段。\n格式：{\"blocks\": [...], \"entityMap\": {}}，每行一个 block，空行 = text=\"\" 的 unstyled block。\nblock.type 常用：unstyled / header-one~six / code-block / ordered-list-item / unordered-list-item / blockquote。\ninlineStyleRanges.style 常用：BOLD / ITALIC / UNDERLINE / CODE / lineThrough / color-red / backgroundColor-#ffff02 / fontSize-20。\noffset/length 以 UTF-16 单位计数（中文一字 1 单位）。\n美化要点：小标题【XX】整段 BOLD、小节间留空行、样例用 code-block、关键词用 CODE 或 color-blue；\n完整支持矩阵见 xiaoya-teacher-skill/references/title_rich_text.md。"
  2. First observedv1.3.3

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, and the description is only 3 characters, offering no behavioral insights. Important behaviors (e.g., the tool creates a question within a paper, requires program_setting with code_answer and test cases, modifies the paper's question list) are entirely absent from the description, relying solely on the input schema.

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

Conciseness2/5

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

At 3 characters, the description is extremely short, but for a complex tool with many nested parameters and sibling distinctions, this is under-specification. Conciseness should not sacrifice necessary context; a slightly longer description that summarizes key aspects would be more valuable.

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?

Given the high complexity (nested objects, many fields, no output schema), the description is far from complete. It does not mention return values, prerequisites (e.g., existing paper), or the effect on the paper's question list. The schema provides detail but the description fails to provide a holistic overview.

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 description coverage is 100%, meaning all parameters have detailed descriptions in the schema. The tool description itself adds no additional parameter meaning, so a baseline score of 3 is appropriate. The description does not compensate or enhance understanding beyond the schema.

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 '创建编程题' clearly states the action (create) and resource (programming question), but does not distinguish it from other create_*_question tools in the sibling list. A more specific description highlighting unique aspects (e.g., 'Creates a coding question with test cases and program settings') would improve differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like create_multiple_choice_question or create_fill_blank_question. Sibling tools suggest a context of exam question creation, but no explicit usage context is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sav1ouR520/xiaoya-teacher-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server