Skip to main content
Glama

bb_submit_assignment

Submits a single standard assignment file after a read-only preview and explicit confirmation, using a 10-minute preview token to verify the course, assignment, and file before writing.

Instructions

单文件标准作业提交。默认只读预览;向用户展示目标与文件并确认后,携原参数及10分钟内的preview_token设置confirm=true。测试和小组作业不支持,不自动重试写入。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course": "<course>",
      "assignment": "<assignment>",
      "file_path": "<file_path>"
    },
    "name": "bb_submit_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
commentNo
confirmNo
file_pathYes
assignmentYes
preview_tokenNo

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
messageYes
completeNo
warningsNo
checked_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, but the description adds behavior the agent could not infer: the first call is a dry-run preview, the write requires a 10-minute-TTL preview_token echoing the original parameters, and failed writes must not be retried automatically. It stops short of stating auth requirements or what a rejection/error looks like, so not a 5.

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?

Three dense clauses with no filler, front-loading the purpose then the workflow then the exclusions. Slightly telegraphic phrasings like "携原参数" require the reader to infer the mechanics, but nothing is redundant.

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?

An output schema exists, so return values need not be described, and the description covers the gating workflow, token lifetime, and unsupported cases. It leaves open what happens on token expiry or partial failure and whether file_path is local or remote, minor gaps for a 6-parameter tool.

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 0%, so the description must carry the load; it does explain the two non-obvious parameters (confirm defaults to preview mode, preview_token is valid for 10 minutes and must accompany the original parameters). It says nothing about course, assignment, file_path, or comment, though those names are largely self-describing.

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?

"单文件标准作业提交" names a specific verb (submit) and a tightly scoped resource (single-file standard assignment), and immediately bounds it against tests and group assignments in the same breath. An agent can tell exactly which submission cases this tool covers without opening the schema.

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?

The description supplies an explicit two-step protocol: the first call is a read-only preview, and only after showing the user the target and file and obtaining confirmation should the agent re-invoke with confirm=true plus the preview_token. It also states the when-not cases (tests and group assignments unsupported) and forbids automatic retry on write failures.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.