Skip to main content
Glama

grade_student_question

Assign a numeric score and optional comment to a student's short-answer or attachment question. Use after previewing the student paper and before submitting the overall mark.

Instructions

[批改 3/4] 给学生某道题打分。

何时调用:仅简答题(type=6)和附件题(type=7)需要;选择/填空/判断/编程系统自动评分,跳过。
score 上限 = query_preview_student_paper 返回的该题 score 字段;未 submit 前可重复打分覆盖。
若整卷已提交批阅,先调用 withdraw_student_mark 重开,再重新打分。
四步流程:query_test_result → query_preview_student_paper → grade_student_question → submit_student_mark。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoreYes批改得分(0 ≤ score ≤ 该题满分,满分从 query_preview_student_paper 的 questions[].score 取)
commentNo批改评语(可为空)
group_idYes课程组id(通过 query_teacher_groups 获取)
answer_idYes学生单题答案id(来自 query_preview_student_paper 的 questions[].answer_id 字段)
record_idYes答题记录id(来自 query_test_result 的 answer_records[].record_id 字段)
publish_idYes发布id(来自 query_group_tasks 的 publish_id 字段)
question_idYes题目id(通过 query_paper 获取)
mark_paper_record_idYes批阅记录id(来自 query_preview_student_paper 的 mark_paper_record_id 字段)
Behavior4/5

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

Given no annotations, the description conveys key traits: can be called multiple times before submission, score upper bound from another tool, and integration with a four-step process. Lacks error behavior or permission info but sufficiently transparent.

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

Conciseness5/5

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

Concise, front-loaded with core action, then usage conditions, then workflow. Every sentence adds value with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers when, why, and prerequisites well within the workflow context. Lacks return value description, but the output is likely minimal (success/failure). Adequate for a step in a multi-tool process.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial context by indicating where each parameter value originates (e.g., query_preview_student_paper, query_test_result), enhancing understanding beyond the schema.

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 'Grade a student's question' and specifies it applies only to short answer (type=6) and attachment (type=7) questions, distinguishing it from auto-graded types and sibling tools like grade_student_paper.

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

Usage Guidelines5/5

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

Explicitly states when to call (only for specific question types) and when not to (auto-graded types), provides score limits, mentions repeatability before submission, and outlines the prerequisite workflow including calling withdraw_student_mark if needed.

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