Skip to main content
Glama

Mark Entry Read

mark_entry_read
Idempotent

Mark one Canvas discussion entry as read by specifying course, topic, and entry IDs, updating only your unread counts.

Instructions

Mark one discussion entry as read for you. Only affects your unread counts.

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>",
      "topic_id": "<topic_id>",
      "entry_id": "<entry_id>"
    },
    "name": "mark_entry_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYesDiscussion entry ID (numeric string). Get it from get_full_topic_view or list_entries.
topic_idYesDiscussion topic ID (numeric string). Get it from list_topics.
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.0.2
    • 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."
    • changedInput schema / properties / entry_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion entry ID (numeric string). Get it from get_full_topic_view or list_entries."
    • changedInput schema / properties / topic_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion topic ID (numeric string). Get it from list_topics."
  2. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover idempotency, non-destructiveness, and open-world reach, so the description earns credit for adding real behavioral context: "for you" scopes the effect to the caller's own read state, and "Only affects your unread counts" bounds the blast radius (no notification emails, no content or other-user impact). What's missing is whether this requires course enrollment or any prior read of the topic.

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?

Two short sentences, zero filler, and the primary action is front-loaded before the effect statement. Every word earns its place.

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

Completeness4/5

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

For a narrow three-parameter mutation with full schema documentation, full annotation coverage, and no output schema, the definition supplies enough to call it correctly. A brief note on selection versus mark_all_entries_read/mark_topic_read is the only meaningful gap.

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%, and each parameter already tells the agent where to obtain the ID (list_courses, list_topics, get_full_topic_view/list_entries). The description adds nothing about the three IDs, 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 ("Mark one discussion entry as read") with an explicit scope qualifier, "one," which implicitly contrasts with the many bulk/adjacent siblings (mark_all_entries_read, mark_topic_read). It never names those siblings, so differentiation is inferable rather than stated.

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?

The description gives no when-to-use guidance, no prerequisites, and no routing to alternatives even though the sibling list contains mark_topic_read, mark_all_entries_read, and get_full_topic_view that an agent must choose between. The only hint is the word "one," which implies granularity but does not state a selection rule.

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