Skip to main content
Glama

canvas_discussion_entries

Fetch discussion topic details and replies as plain text for a Canvas course, with an optional limit on returned replies.

Instructions

讨论主题详情 + 回帖列表(正文已转纯文本)。

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": "<course>",
      "topic": "<topic>"
    },
    "name": "canvas_discussion_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo回帖条数,默认 20。
topicYes讨论主题 id 或标题关键词。
courseYes课程 id 或名称关键词。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses only one behavioral trait: bodies are converted to plain text. It says nothing about whether the call is read-only, whether enrollment in the course is required, how the reply list is paginated, or what the result looks like, despite there being no output schema.

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 short sentence with no wasted words, and the essential resource is front-loaded. It is efficient, though its brevity is achieved partly by omitting information.

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

Completeness2/5

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

With no annotations and no output schema, the description should explain the return shape and pagination behavior, but it does not. For a tool that returns both a topic and a variable-length reply list, this is under-specified.

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 the schema already explains course, topic, and limit (including the default of 20 and the cap of 200). The description adds no parameter-level meaning beyond the schema; the baseline of 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?

The description states a specific verb+resource pair: it returns discussion topic detail plus the reply list, with bodies converted to plain text. An agent can tell what the tool fetches. However, it never distinguishes itself from the sibling canvas_discussions, which likely also concerns discussions, so the boundary is left ambiguous.

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 explicit when-to-use or when-not-to-use guidance, and the obvious alternative (canvas_discussions) is not mentioned. Usage can only be inferred from the resource named in the description.

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