Skip to main content
Glama

update_teach_target

Update student or class profile fields such as name, grade, textbook, subject, parent phone, or color. Only the fields you specify are modified; others remain unchanged.

Instructions

改教学对象档案(学生/班级信息修改)→ :9090。返回 {ok, id, updated:['basic'/'profile']}。

create_teach_target 只能建、建完改不了——本工具补上「改」:改名/年级/教材/学科/家长手机/色,或整体覆写肖像。 🔴 只改传入的字段:不传的保持原值(BE updateById NOT_NULL 跳空);基本维不动肖像,肖像走独立整覆写。 🔴 target_type 必传(BE 靠它选学生表/班级表);改肖像务必先 get_student_profile 取全量再整体回传(传 {} 会清空)。 参数: target_id : 对象 id(字符串雪花号)——必填 target_type : 'student' | 'class'——必填(决定改哪张表) name : 新对象名(不传=不改) grade_no : 年级 1-12(字典 biz_edu_grade) grade_year : grade_no 生效学年起始年(如 2026) textbook_edition : 教材版本码(biz_edu_edition:1浙教/2人教/3北师大/4苏教,兼容中文标签) subject : 学科码(biz_edu_subject:1数学/2科学/3语文/4英语,兼容中文标签) parent_phone : 家长手机号(仅学生) color : 日历着色 profile : 肖像 dict(整体覆写,非增量!结构见 create_teach_target 的 profile 说明)—— 改肖像典型流程 = get_student_profile 读回 → 本地改 → 整体传回

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
colorNo
profileNo
subjectNo
grade_noNo
target_idYes
grade_yearNo
target_typeYes
parent_phoneNo
textbook_editionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Details that only passed fields are updated, profile is overwritten entirely, and warns about clearing profile. No annotations, so description carries full burden; it does so comprehensively.

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?

Well-structured with purpose upfront, key warnings highlighted, and parameter list. Slightly long but justified by complexity.

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

Completeness5/5

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

Given no annotations and output schema present in context, description covers return value, input constraints, and edge cases thoroughly.

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

Parameters5/5

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

Schema has 0% description coverage but description provides detailed semantics for all parameters including required fields, data types, and special behaviors.

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?

Clearly states it updates teaching target records (student/class info) and explicitly distinguishes from sibling create_teach_target which only creates.

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 says when to use this tool vs create_teach_target and advises prerequisite step for profile updates.

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/RuntimeAll/teacher-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server