Skip to main content
Glama

bind_paper_slot

Bind an existing paper to a lesson slot, unbind it, or mark the entire lesson as ready. Manages paper-slot relationships after composition.

Instructions

🔴 PRD-B-101 备课卷位绑定管理(绑既有卷 / 解绑 / 标记已备好)→ 备课线。返回 {ok, paper_slots, prep_state}。

备课主路 = 组卷时直接带 lesson_id+slot_seq 建卷即自动绑(create_paper/compose_paper); 本工具是事后管理:把已有卷挂到卷位(D7 兜底)、解绑、或手动标记整课次已备好。 🔴 备课卷私有,本工具不含任何公开化能力(绝不 set-public)。 参数: lesson_id : 课次 id(字符串雪花号)——必填。 slot_seq : 卷位序号(≥1)——action=bind/unbind 必填;action=manual_ready 忽略(课次级)。 action : 动作枚举—— 'bind' 绑既有卷到卷位(传 paper_id,必须真实存在且归我;BE 自动置该卷 paper_kind='2') 'unbind' 解绑卷位(卷留库不删;🔴 解绑会自动清该课次 manual_ready=false) 'manual_ready' 手动标记整课次备课态(传 ready;0 卷位课次 → BE 400) paper_id : action=bind 时必填(要挂的既有卷 id,字符串雪花号)。 ready : action=manual_ready 时的目标态(True=已备好,默认 True)。 返回: {ok, paper_slots:[...], prep_state:'0未备/1备课中/2已备好'};异常 → {ok:false, error}。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readyNo
actionNobind
paper_idNo
slot_seqNo
lesson_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description fully carries the burden. It details behaviors: return structure, side effects of unbind (resets manual_ready), parameter constraints, and the fact that it never makes items public. All important traits are disclosed.

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 sections and bullet points, but slightly verbose with emojis and repeated emphasis. However, for the complexity (3 actions, conditional params), the length is justified and information is front-loaded.

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 the tool complexity, output schema existence, and lack of annotations, the description covers input, output, behavior, and context. It contrasts with relevant siblings and states constraints (no public). Complete and sufficient for agent usage.

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 coverage is 0%, meaning no descriptions in schema. The description compensates fully by explaining each parameter: lesson_id required, slot_seq conditionally required, action enum with three values and their conditions, paper_id for bind, and ready for manual_ready with default. Adds critical context beyond schema structure.

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 tool's purpose: managing post-creation binding, unbinding, and marking ready for lesson paper slots. It distinguishes from the main path (create_paper/compose_paper) which handles automatic binding during creation.

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 describes when to use this tool (after creation) and when to use other tools (during creation). Also warns about no public ability, providing clear boundaries.

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