Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Discussion Entry Details

get_discussion_entry_details
Read-only

Retrieve detailed information for a specific Canvas discussion entry, including all replies, by supplying course, topic, and entry identifiers.

Instructions

Get detailed information about a specific discussion entry including all its replies.

Input Schema

NameRequiredDescriptionDefault
entry_idYesDiscussion entry ID
group_idNoCanvas group ID, to read a discussion inside a group space instead of the course (default: None). Discussions that students start in a group exist only there. The group must belong to the course.
topic_idYesDiscussion topic ID
include_repliesNoFetch and include replies (default: True)
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / group_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Canvas group ID, to read a discussion inside a group\nspace instead of the course (default: None). Discussions that\nstudents start in a group exist only there. The group must\nbelong to the course."
+}
  2. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  3. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / entry_id / description
      Added value: +"Discussion entry ID"
    • removedInput schema / properties / entry_id / title
      Removed value: -"Entry Id"
    • addedInput schema / properties / include_replies / description
      Added value: +"Fetch and include replies (default: True)"
    • removedInput schema / properties / include_replies / title
      Removed value: -"Include Replies"
    • addedInput schema / properties / topic_id / description
      Added value: +"Discussion topic ID"
    • removedInput schema / properties / topic_id / title
      Removed value: -"Topic Id"
    • removedInput schema / title
      Removed value: -"get_discussion_entry_detailsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_discussion_entry_detailsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_discussion_entry_detailsArguments"
  5. First observed

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already covers the safety profile, so the description only needs to add context. Instead, 'including all its replies' is stated unconditionally even though include_replies defaults true but is toggleable, and nothing is said about permissions, group-scoped entries, or response size for large threads.

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?

One sentence, zero filler, and the core purpose is front-loaded. It is efficient but leans on a claim about replies that the schema treats as optional.

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?

With annotations covering read-only safety and full schema coverage, the description is minimally adequate. For a 5-parameter tool with group scoping and reply toggles, it should still say how it differs from the sibling discussion-entry tools.

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 all five parameters (including group_id scoping and include_replies) are already documented in the schema. The description adds no syntax, format, or interaction detail beyond that, so the baseline 3 applies.

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 detailed information about a specific discussion entry') and adds that replies are included. It does not, however, distinguish itself from close siblings such as get_discussion_with_replies, get_discussion_topic_details, or list_discussion_entries, which an agent must choose between.

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 and no mention of alternatives. The agent is left to infer that this is for a single entry versus list_discussion_entries or get_discussion_with_replies.

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