Skip to main content
Glama

create_short_answer_question

Add a short answer question to a paper, supporting rich text, Markdown, and inline assets for educational assessments.

Instructions

创建简答题

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes试卷ID(通过 query_group_tasks 获取)
questionYes
need_parseNotrue 返回纯文本(plain),false 返回原始富文本结构(raw)
need_detailNo是否在返回中包含完整题目内容(选项、答案等),仅需确认成功时设为 false

Schema Changelog

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

  1. Changed8 schema fields changedv1.5.2
    • changedInput schema / $defs / ShortAnswerQuestion / properties / answer / description
      Previous value: -"参考答案纯文本,与 answer_raw 二选一"New value: +"参考答案纯文本,与 answer_md/answer_raw 三选一"
    • addedInput schema / $defs / ShortAnswerQuestion / properties / answer_assets
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "参考答案 Markdown 引用的资源列表,仅与 answer_md 一起使用,格式同 title_assets",
      +  "title": "Answer Assets"
      +}
    • addedInput schema / $defs / ShortAnswerQuestion / properties / answer_md
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "参考答案 Markdown,与 answer/answer_raw 三选一,工具会自动转为小雅 Draft.js 富文本;图片/附件用 asset://id 占位并配合 answer_assets。",
      +  "title": "Answer Md"
      +}
    • changedInput schema / $defs / ShortAnswerQuestion / properties / answer_raw / description
      Previous value: -"参考答案富文本,与 answer 二选一"New value: +"参考答案富文本,与 answer/answer_md 三选一"
    • changedInput schema / $defs / ShortAnswerQuestion / properties / title / description
      Previous value: -"题干纯文本(与 title_raw 二选一)。只在一两行的简单题目用;结构化题干(OJ、分小节)走 title_raw。"New value: +"题干纯文本(与 title_md/title_raw 三选一)。只在一两行的简单题目用。"
    • addedInput schema / $defs / ShortAnswerQuestion / 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 / ShortAnswerQuestion / 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 / ShortAnswerQuestion / 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

D1.7/5.0
Behavior1/5

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It only states the purpose without mentioning side effects, required permissions, or any other behavioral traits.

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?

The description is extremely short (4 Chinese characters) but lacks substantive content. It is under-specified rather than concise, failing to provide useful information.

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

Completeness1/5

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

Given the complexity of the tool (many parameters, nested question object, sibling tools) and absence of output schema, the description fails entirely to provide needed context about usage, return values, or the internal structure of the question object.

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 high (75%), so the description does not need to repeat parameter info. Baseline 3 applies; the description adds no value beyond the schema.

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

Purpose2/5

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

The description '创建简答题' is a tautology, essentially repeating the Chinese translation of the tool name. It does not provide any new information about what the tool does, making it minimally helpful for distinguishing from sibling tools.

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

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus alternatives (e.g., create_question, other specific question creators). No prerequisites, exclusions, or context for when this tool is appropriate.

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

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