Skip to main content
Glama
kaeru333

ScienceTokyoLMS-mcp

by kaeru333

submit_assignment_files

Preview assignment file validation and constraints, then confirm to submit to Moodle.

Instructions

課題にファイルを提出する (2 段階: 既定はプレビュー).

confirm=False (既定) では Moodle へ一切書き込まず,課題の説明文・提出制約・ 各ファイルの検査結果のみを返す.この結果を受け取ったら,各ファイルを Read で 開いて内容を確認し,課題の説明文 (assignment_intro) と突き合わせて,提出物が 課題の意図に合っているかを必ず判断すること. 問題がなければ confirm=True で 同じ引数で再度呼び出すと実提出する.

Args: assignment_id: 課題 (assignment) の ID.list_assignments で取得できる. file_paths: 提出するローカルファイルのパス (複数可). confirm: True で実提出.False (既定) はプレビューのみ (書き込みなし).

Returns: 提出プレビュー,または提出結果 (:class:SubmissionPlan).

Raises: ValueError: confirm=True だが検査に通らないファイルや個数超過がある場合.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
file_pathsYes
assignment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYes各提出予定ファイルの検査結果.
notesNoClaude / ユーザーへの注意書き (確認を促す文言).
all_okYes全ファイルが提出可能な状態か.
confirmedNo実際に提出したか (False はプレビュー).
constraintsYes課題のファイル提出制約.
assignment_idYes課題 (assignment) の ID.
assignment_introNo課題の説明文 (HTML 除去済み).
assignment_titleYes課題のタイトル.
submitted_for_gradingNo採点提出まで確定したか.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that confirm=False does not write to Moodle and returns preview, while confirm=True performs actual submission. It also mentions ValueError for invalid files. However, it does not specify if submission is irreversible or any permission requirements.

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?

Description is well-structured with sections for Args, Returns, Raises. It is slightly verbose but every sentence adds value. Could be trimmed slightly without losing clarity.

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?

Given the presence of output schema, description adequately covers workflow, parameters, and exceptions. It could mention how to obtain assignment_intro, but overall complete for a submission tool.

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?

Despite 0% schema coverage, the description's Args block fully explains each parameter: assignment_id (from list_assignments), file_paths (local paths), confirm (default false for preview). This adds significant meaning 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 the tool's purpose: 'Submit files to assignment (2 steps: default is preview)'. It uses a specific verb ('submit') and resource ('assignment files'), and distinguishes from sibling tools which are primarily read/list actions.

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?

Description explicitly explains the two-step workflow: use confirm=False for preview (no write) and confirm=True for actual submission. It instructs to verify files against assignment_intro before confirming, providing clear when-to-use guidance.

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/kaeru333/ScienceTokyoLMS-mcp'

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