Skip to main content
Glama

update_paper_randomization

Configure randomization settings for exam papers, including question order, option order, and scoring type.

Instructions

更新试卷的题目和选项随机化设置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes试卷ID(通过 query_group_tasks 获取)
question_shuffleNo题目顺序随机(1=关闭 2=开启)
option_shuffleNo选项顺序随机(1=关闭 2=开启,仅对选择题生效)
question_score_typeNo计分方式(1=严格计分:全对才得分 2=宽分模式:按正确选项比例得分)
Behavior2/5

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

No annotations are provided, so the description must bear the full burden. It only states that the tool updates settings but fails to disclose important behavioral traits such as whether changes are permanent, what happens to existing randomization, or any prerequisites (e.g., paper must exist). As a mutation tool, this lack of transparency 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 a single clear sentence with no unnecessary words. It efficiently conveys the core purpose. However, it could be slightly improved by adding context that is currently missing.

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 (4 parameters, mutation, no output schema), the description is too terse. It omits critical context such as return values, side effects, and prerequisites. The schema provides parameter details, but the description should complete the picture.

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%; all four parameters are described in the schema. The description adds no additional meaning beyond the schema. Under the rule that high coverage yields a baseline of 3, this score is appropriate.

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

Purpose5/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 the resource '试卷的题目和选项随机化设置' (paper question and option randomization settings), which includes both shuffling and scoring type. This distinguishes it from sibling tools like update_paper_question_order (order only) and update_question_options (options content).

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. Sibling tools like update_paper_question_order or update_question exist, but no when-to-use or when-not-to-use information is provided.

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