Skip to main content
Glama

get_discussions

Retrieve discussion topics for a Canvas course using its course ID, so you can review and reference course conversations.

Instructions

Get discussion topics for a Canvas course

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>"
    },
    "name": "get_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesCanvas course ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and provides almost none: it never says the operation is read-only, whether results are paginated or sorted, or whether it includes pinned/closed/locked topics. 'Get' weakly implies a read, but that is left to inference rather than disclosed.

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?

One short, front-loaded sentence with no filler or redundancy. Every word contributes to identifying the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with no output schema, the description is minimally adequate: it identifies the resource but leaves the shape of the returned data (topic titles, IDs, reply counts, pagination) and its read-only nature unstated. An agent can call it correctly but cannot predict what it will get back.

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?

There is a single parameter (course_id) with 100% schema description coverage, so the schema already explains it fully and the description adds no syntax, format, or constraint detail. A baseline 3 is appropriate since the schema does the work and the description neither compensates nor detracts.

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?

States a specific verb and resource ('Get discussion topics') scoped to a Canvas course, so an agent can tell it retrieves discussion topics rather than announcements or assignments. It does not explicitly distinguish itself from near-neighbors like get_announcements, which in Canvas are a related discussion type, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no note about required course enrollment or permissions, and no pointer to a sibling such as get_announcements for announcement-type content. The only implied usage is 'inside a course', which the required course_id already conveys.

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