Skip to main content
Glama

Reply To Entry

reply_to_entry
Destructive

Post a reply to a specific Canvas discussion entry, with a preview-and-confirm step before the class-visible message is sent.

Instructions

Reply to one discussion entry. Visible to the whole class. Use post_entry for a new top-level post. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

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

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
messageYesMessage text. Plain text or simple HTML.
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.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed4 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."
    • addedInput schema / properties / message / description
      Added value: +"Message text. Plain text or simple HTML."
    • changedInput schema / properties / topic_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion topic ID (numeric string). Get it from list_topics."
  3. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, destructive, open-world mutation, so the description's job is supplemental context, and it delivers: it discloses that the content becomes visible to the whole class and details the preview/confirm_token safety flow that the annotations cannot express. The bracketed "[NEEDS CONFIRMATION: ...]" phrasing reads like an internal note rather than polished documentation, and it doesn't say what happens if the token is stale or reused.

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?

Front-loads the purpose and visibility consequence in two short sentences, then the alternative, then the protocol. The bracketed confirmation block is longer than the rest combined and its bracket/colon formatting is awkward, but every sentence carries operational information.

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 six-parameter mutation with no output schema, the description covers what an agent most needs: scope of visibility, sibling routing, and the mandatory confirmation handshake. Gaps are minor — no mention of what the preview returns or whether a reply can later be edited by edit_my_entry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all six fields; the description still earns credit by explaining the relationship between confirm and confirm_token that the schema describes only locally ("Set to true together with confirm_token..."). It clarifies the two-invocation pattern the parameters exist to serve, which is meaning beyond the individual field docs.

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

Purpose5/5

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

States a specific verb and resource ("Reply to one discussion entry") and immediately distinguishes itself from the sibling post_entry for new top-level posts. An agent can separate reply_to_entry from post_entry, edit_my_entry, and list_entry_replies without opening any schema.

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

Usage Guidelines4/5

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

Names the alternative (post_entry) and the condition that selects it, and spells out the exact two-call confirmation protocol: preview first, show the user, then re-call with confirm=true plus confirm_token. It does not cover adjacent cases such as when to reply versus editing or deleting one's own entry, but the primary routing decision is explicit.

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