omnivox-mcp

Get Assignment Submit Link

get-assignment-submit-link

Read-onlyIdempotent

Generates a short, pre-authenticated Omnivox link that opens an assignment's hand-in page so users can upload files in their own browser; the link expires in 15 minutes and does not submit work.

Instructions

Get a short link that opens the Omnivox hand-in page for an assignment, already logged in. Give it to the user so they can upload their file in their own browser — this tool never submits anything itself. Link expires after 15 minutes. Fails if online submission is closed for the assignment, or if the server has no public URL (MCP_SERVER_URL).

Input Schema

Name	Required	Description
`term_id`	No	Academic term ID in YYYYN format (e.g. '20263').
`course_id`	Yes	Full course ID including group number (e.g. '2433C5EM.1012'). Always required, even for document and assignment downloads where the item ID alone looks sufficient.
`assignment_id`	Yes	Assignment ID (UUID) from get-course-assignments.

Output Schema

Name	Required	Description	Default
`msg`	Yes
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.7.0Oct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial context beyond annotations: the link is pre-authenticated, expires after 15 minutes, fails when online submission is closed, and fails when the server lacks a public URL. It also clarifies the important non-obvious behavior that the tool never submits files.

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?

Three focused sentences, front-loaded with the core purpose, immediately followed by intended usage, then expiry and failure modes. No filler or redundancy.

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 an output schema and safety annotations already present, the description supplies the remaining operational context an agent needs: what the link is for, that it is not a submission action, expiration, and failure conditions. Nothing essential is missing.

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 100%, so parameters are already well documented in the schema. The description adds no additional parameter-level guidance beyond what the schema provides, which is acceptable at baseline 3.

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?

States a specific verb and resource: get a short link that opens the Omnivox hand-in page for an assignment. It clearly distinguishes the tool from submission itself and from related file-download tools by framing it as a hand-in/upload link, not a file retrieval tool.

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

Usage Guidelines4/5

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

Explicitly says to give the link to the user so they can upload in their own browser, and clarifies the tool never submits anything itself. It also states failure conditions. However, it does not explicitly route against siblings like get-assignment-file-link or get-assignment-detail beyond the hand-in framing.

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