Skip to main content
Glama

Submit Assignment URL

submit_assignment_url
Destructive

Submit a website URL for a Canvas assignment that accepts URL submissions, using a preview and confirmation so the instructor sees it as an attempt.

Instructions

Submit a website URL for an assignment that accepts URL submissions. Your instructor sees it and it counts as a submission attempt. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

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_id": "<course_id>",
      "assignment_id": "<assignment_id>",
      "url": "<url>"
    },
    "name": "submit_assignment_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull web address to submit, starting with https://.
commentNoComment text, visible to your instructor.
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
assignment_idYesAssignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changedv1.0.2
    • changedInput schema / properties / assignment_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Assignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments."
    • addedInput schema / properties / comment / description
      Added value: +"Comment text, visible to your instructor."
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • addedInput schema / properties / url / description
      Added value: +"Full web address to submit, starting with https://."
  3. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: the instructor sees the submission and it 'counts as a submission attempt,' which signals finality and attempt consumption. It also discloses the two-step preview/confirm-token mechanism, something no annotation conveys. It stops short of saying whether a submitted URL can be replaced or withdrawn.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and consequence are front-loaded in two tight sentences with no filler. However, the bracketed '[NEEDS CONFIRMATION: ...]' meta-note is unpolished and reads like an editorial artifact, which adds ambiguity precisely where the critical calling instructions live.

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?

For a mutation tool with no output schema, it covers purpose, eligibility, the confirmation protocol, and the post-submission consequence, which is the core an agent needs. It omits what the preview payload contains and what happens on failure (e.g., assignment not accepting URL submissions, already-submitted state).

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description goes beyond the schema by explaining the relationship and ordering between the preview call, confirm_token, and confirm=true. That sequencing is the part the schema only states in isolation. The comment parameter's visibility is already covered by the schema and is not elaborated further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource ('Submit a website URL') plus the eligibility constraint ('for an assignment that accepts URL submissions'), which implicitly separates it from submit_assignment_text and submit_assignment_file. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

It gives concrete when-to-use context ('an assignment that accepts URL submissions') and a precise invocation protocol: call once for a preview, show it to the user, then call again with confirm=true and the token only after approval. The '[NEEDS CONFIRMATION: ...]' wrapper reads as an unresolved note rather than settled guidance, which weakens an otherwise useful instruction.

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

Deploy Server

Other Tools