Skip to main content
Glama

canvas_announcements

Retrieve course announcements by course ID or name, returning each announcement’s time, title, and link for quick review.

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

Input Schema

NameRequiredDescriptionDefault
courseYes课程 id 或名称关键词。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 disclosure burden, yet it only lists three returned fields. It says nothing about read-only nature, whether results are scoped to one course or all enrolled courses, ordering, volume, or failure modes such as an unknown course keyword.

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?

There is no wasted wording, but the definition is a bare noun phrase with a parenthetical; it is under-specified rather than well-structured, and it front-loads the resource without ever stating the operation.

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 one-parameter read tool with no output schema, disclosing the returned fields (time / title / link) covers part of the return-value burden. Still missing are the operation verb, result scope, and any behavioral caveats, which leaves the agent with gaps before calling it.

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 and the schema documents it fully as a course id or name keyword. The description adds no extra meaning about matching behavior (id vs. fuzzy keyword), so the baseline of 3 for high schema coverage applies.

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

Purpose3/5

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

The description names the resource (course announcements) and the fields returned (time / title / link), which distinguishes it reasonably from siblings like canvas_deadlines and canvas_inbox. However, it never states the action — nothing says whether it lists, fetches, or searches announcements — so the agent must infer that it is a per-course listing.

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?

No when-to-use guidance is given: no mention of when to prefer this over canvas_deadlines, canvas_courses, or canvas_discussions, and no prerequisites such as enrollment or authentication. The agent can only guess usage from the tool name.

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