Skip to main content
Glama

update_question

Update any question's configuration including title, score, required status, automatic scoring, and programming settings for coding questions.

Instructions

更新任意题目的通用配置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoreNo题目分值(大于等于0的整数)
titleNo题干纯文本(与 title_md/title_raw 三选一)。只在一两行的简单题目用。
requiredNo是否必答(1=否 2=是)
title_mdNo题干 Markdown(与 title/title_raw 三选一)。工具会自动转为小雅 Draft.js 富文本;适合 AI 输出的分节题干、列表、代码块、样例输入输出;图片/附件用 asset://id 占位并配合 title_assets。
title_rawNo题干富文本(Draft.js 格式),与 title/title_md 三选一,优先本字段。 格式:{"blocks": [...], "entityMap": {}},每行一个 block,空行 = text="" 的 unstyled block。 block.type 常用:unstyled / header-one~six / code-block / ordered-list-item / unordered-list-item / blockquote。 inlineStyleRanges.style 常用:BOLD / ITALIC / UNDERLINE / CODE / lineThrough / color-red / backgroundColor-#ffff02 / fontSize-20。 offset/length 以 UTF-16 单位计数(中文一字 1 单位)。 美化要点:小标题【XX】整段 BOLD、小节间留空行、样例用 code-block、关键词用 CODE 或 color-blue; 完整支持矩阵见 xiaoya-teacher-skill/references/title_rich_text.md。
parse_modeNo富文本解析模式:plain=纯文本,raw=原始结构,markdown=标准 Markdown + assetsplain
descriptionNo答案解析或补充说明;编程题参考代码请填写到 program_setting.code_answer
question_idYes题目id(通过 query_paper 获取)
title_assetsNo题干 Markdown 引用的资源列表,仅与 title_md 一起使用。格式:[{"id":"img_1","type":"image","name":"图.png","file_path":"/abs/图.png"}];图片占位:![说明](asset://img_1),附件占位:[附件名](asset://file_1)。
automatic_statNo是否开启自动评分(1=关闭 2=开启)
automatic_typeNo自动评分类型(1=精确匹配+有序 2=部分匹配+有序 11=精确匹配+无序 12=部分匹配+无序)
is_split_answerNo是否允许每个空有多个答案(仅填空题,true=允许)
program_settingNo编程题配置(仅编程题需要,规则同 PROGRAM_SETTING_DESC)
Behavior2/5

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

No annotations are present, so the description must carry behavioral disclosure. It does not mention whether the update is partial or full, idempotent, or what side effects occur. The schema implies optional fields for partial updates, but this is not stated.

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

Conciseness3/5

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

The description is a single sentence, which is concise but does not provide substantial value. It is not front-loaded with critical information; it merely restates the function.

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 13 parameters and no output schema, the description is insufficient. It does not explain update semantics, error handling, or typical use cases. The schema covers parameters well, but the description adds no context.

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%, so baseline is 3. The description adds no additional meaning beyond the schema. It does not explain parameter relationships or usage patterns.

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 tool updates general configuration of any question, but does not differentiate from siblings like update_question_options or update_code_test_cases. It is specific about the resource but lacks sibling distinction.

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. It does not mention prerequisites, limitations, or context where other tools are preferred.

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