Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Remote Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Tool Launch URL

get_tool_launch_url
Read-onlyIdempotent

Generate a one-time launch URL for an external LTI tool in a Canvas course so users can open it directly in a browser. Get tool_id from list_external_tools; the URL expires quickly.

Instructions

Get a one-time launch URL for an external (LTI) tool in a course, so you can open it directly in a browser. Read-only. Get tool_id from list_external_tools. The URL expires quickly.

Input Schema

NameRequiredDescriptionDefault
urlNoOptional launch URL of a specific tool resource, if the tool needs one.
tool_idNoExternal tool ID (numeric string). Get it from list_external_tools.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.3
    • 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 / tool_id / description
      Added value: +"External tool ID (numeric string). Get it from list_external_tools."
    • addedInput schema / properties / url / description
      Added value: +"Optional launch URL of a specific tool resource, if the tool needs one."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

While annotations cover safety, the description adds critical behavioral traits such as the URL being 'one-time' and 'expir[ing] quickly,' providing necessary operational context that standard metadata lacks.

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?

The description is concise, front-loaded with its primary purpose, and efficiently integrates the essential constraints (read-only, expiration).

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 simplicity of the input schema and the richness of the annotations (safety, idempotency), the description provides all necessary context for a successful and correct invocation.

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?

With 100% schema coverage, the description adds value by emphasizing the required source of `tool_id` ('Get tool_id from list_external_tools'), which is a behavioral constraint on parameter input rather than just a data description.

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 is highly specific, stating it retrieves a 'one-time launch URL for an external (LTI) tool,' which clearly defines the operation and resource.

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?

It provides explicit workflow guidance by instructing the agent to retrieve the necessary `tool_id` from the `list_external_tools` function, making the dependency clear.

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