Skip to main content
Glama

create_multiple_choice_question

Create a multiple-choice question for a paper with customizable stem, options, correct answers, and explanations. Supports plain text, Markdown, or rich text input.

Instructions

创建多选题

Input Schema

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

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

With no annotations, the description carries the full burden of disclosing behavioral traits. The description '创建多选题' provides no information about side effects, return values, permissions, or any other behavioral aspects.

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

Conciseness1/5

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

The description is extremely concise (one phrase) but lacks any structure or useful content. It fails to provide value beyond the tool name, making it under-specified rather than efficiently concise.

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 input schema with nested objects and many options, the description is woefully incomplete. It does not explain the creation process, return values, or how to use the parameters, leaving the agent with insufficient 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 coverage is 75%, meaning the schema already describes most parameters. The description adds no new meaning beyond the schema, as it only states the tool's function. The schema's parameter descriptions are detailed, so the description does not need to compensate.

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

Purpose3/5

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

The description '创建多选题' translates to 'Create multiple choice question', which states the verb and resource but lacks specificity to distinguish it from sibling tools like create_single_choice_question or create_true_false_question. The purpose is clear but minimal.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention any prerequisites or 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