Skip to main content
Glama

update_short_answer_answer

Update the reference answer for a short-answer question by specifying plain text, Markdown, or raw rich text content, optionally with assets.

Instructions

[仅限简答题]更新简答题参考答案

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answerNo参考答案纯文本,与 answer_md/answer_raw 三选一
answer_mdNo参考答案 Markdown,与 answer/answer_raw 三选一,工具会自动转为小雅 Draft.js 富文本;图片/附件用 asset://id 占位并配合 answer_assets。
answer_rawNo参考答案富文本,与 answer/answer_md 三选一
parse_modeNo富文本解析模式:plain=纯文本,raw=原始结构,markdown=标准 Markdown + assetsplain
question_idYes题目id(通过 query_paper 获取)
answer_assetsNo参考答案 Markdown 引用的资源列表,仅与 answer_md 一起使用,格式同 title_assets
answer_item_idYes答案项id
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states 'update' without detailing side effects, permissions, or idempotency. For a mutation tool, this is insufficient.

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?

The description is extremely concise (one short sentence). It is front-loaded and immediately clear, though it may be too brief for full comprehension.

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 has 7 parameters, no annotations, and no output schema, the description is inadequate. It lacks context on return values, side effects, and usage scenarios, making it incomplete for an agent.

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 schema already explains parameters. The description adds no additional meaning beyond the title, resulting in baseline performance.

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 specifies the tool updates reference answers for short answer questions. It clearly identifies the resource and action, distinguishing it from sibling tools like update_fill_blank_answer. However, it does not elaborate on 'reference answer' scope.

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

Usage Guidelines3/5

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

The description implies use only for short answer questions, but provides no explicit guidance on when to use this versus alternatives. No context on prerequisites or exclusions.

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