Skip to main content
Glama

update_question

Update any question's title, score, description, answer settings, and programming configuration for coding problems.

Instructions

更新任意题目的通用配置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
question_idYes题目id(通过 query_paper 获取)
titleNo题干纯文本(与 title_raw 二选一)。只在一两行的简单题目用;结构化题干(OJ、分小节)走 title_raw。
title_rawNo题干富文本(Draft.js 格式),与 title 二选一,优先本字段。 格式:{"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。
scoreNo题目分值(大于等于0的整数)
descriptionNo答案解析或补充说明;编程题参考代码请填写到 program_setting.code_answer
requiredNo是否必答(1=否 2=是)
is_split_answerNo是否允许每个空有多个答案(仅填空题,true=允许)
automatic_statNo是否开启自动评分(1=关闭 2=开启)
automatic_typeNo自动评分类型(1=精确匹配+有序 2=部分匹配+有序 11=精确匹配+无序 12=部分匹配+无序)
program_settingNo编程题配置(仅编程题需要,规则同 PROGRAM_SETTING_DESC)
parse_modeNo富文本解析模式:plain=纯文本,raw=原始结构plain
Behavior2/5

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

With no annotations provided, the description only indicates a generic update operation. It does not disclose behavioral details such as permission requirements, side effects, or immutability of fields not mentioned.

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 short sentence, which is concise but lacking structure. It could be expanded to list typical fields or provide usage context without being verbose.

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 tool's complexity (11 parameters, no output schema, no annotations), the description is too brief. It does not explain what 'general configuration' entails or how to use the tool effectively, relying entirely on schema documentation.

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 the baseline is 3. The description itself does not add parameter-specific meaning; it only provides a high-level purpose, neither enhancing nor detracting from schema detail.

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 verb 'update' and resource 'general configuration of any question', distinguishing it from sibling tools specialized for specific question components (e.g., update_question_options). However, it does not explicitly differentiate from all siblings.

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 alternative update tools like update_question_options or update_fill_blank_answer. The agent must infer intent from schema and context.

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