Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Conversation Details

get_conversation_details
Read-only

Retrieve detailed Canvas conversation data and messages without marking them read. Use it to review message history while keeping unread status intact.

Instructions

Get detailed conversation information with messages.

Viewing never marks the conversation read; use mark_conversations_read for that.

Input Schema

NameRequiredDescriptionDefault
conversation_idYesConversation ID
include_messagesNoInclude all messages

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • removedInput schema / properties / auto_mark_read
      Removed value: -{
-  "default": true,
-  "description": "Mark as read when viewed",
-  "type": "boolean"
-}
  2. Changed9 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / auto_mark_read / description
      Added value: +"Mark as read when viewed"
    • removedInput schema / properties / auto_mark_read / title
      Removed value: -"Auto Mark Read"
    • addedInput schema / properties / conversation_id / description
      Added value: +"Conversation ID"
    • removedInput schema / properties / conversation_id / title
      Removed value: -"Conversation Id"
    • addedInput schema / properties / include_messages / description
      Added value: +"Include all messages"
    • removedInput schema / properties / include_messages / title
      Removed value: -"Include Messages"
    • removedInput schema / title
      Removed value: -"get_conversation_detailsArguments"
    • removedOutput schema / title
      Removed value: -"get_conversation_detailsDictOutput"
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_conversation_detailsArguments"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds a genuinely non-obvious trait: viewing does not mark the conversation read. That is the kind of side-effect disclosure that saves an agent from a wrong assumption, though nothing is said about pagination or message volume limits.

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?

Two short sentences with no filler, and the read-state caveat follows immediately after the purpose. Efficient, though the caveat could have been folded in more tightly.

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?

With an output schema present and annotations covering the safety profile, the description only needs to cover the read-state semantics, which it does. The remaining gap (how to discover conversation IDs) is minor for a two-parameter read tool.

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 coverage is 100%, so both parameters are documented structurally; the phrase 'with messages' loosely maps to include_messages, but the description adds no detail on the default (true) or on the accepted ID types. Baseline 3 applies when the schema does the work.

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 conversation information with messages'), clearly distinguishing it from the listing sibling list_conversations. It stops short of explicitly naming the sibling used to enumerate conversations, but the purpose is unambiguous.

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?

Gives clear usage context by naming mark_conversations_read as the alternative for marking read, which is the most likely point of confusion. It does not mention how to obtain a conversation_id (e.g., via list_conversations), leaving a small gap.

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