Skip to main content
Glama

Read conversation

bb_get_conversation
Read-only

Read every message in a Blackboard conversation by course ID and conversation ID to review the full discussion thread. Retrieves complete message history for context.

Instructions

Read every message in a conversation.

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": {
      "courseId": "<courseId>",
      "conversationId": "<conversationId>"
    },
    "name": "bb_get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds only the scope phrase "every message", and stays silent on pagination or result limits, message ordering, permission failures, and whether empty conversations return an empty list — all relevant for a read tool with 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?

A single short sentence with no filler, and the resource and scope are front-loaded. Its brevity is superficially good, but it reflects under-specification rather than economical writing.

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?

This is a simple two-parameter read tool, but with no output schema and no schema descriptions, the definition should at minimum say what the response contains (message bodies, authors, timestamps) and whether results are paged. None of that is present, so the definition is underpowered for its job.

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

Parameters2/5

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

The input schema has 0% description coverage for both required parameters, so the description carries the full burden of explaining them. It never mentions courseId or conversationId, their ID formats, or the relationship between them (course-scoped conversation), leaving the agent to guess values from parameter names only.

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 gives a specific verb ("Read") and resource ("conversation") and adds a scope qualifier, "every message in a conversation", that tells an agent it returns the full message list rather than metadata. It does not distinguish this from siblings such as bb_get_discussion_thread, though no conversation-specific alternative is offered in the supplied catalog.

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 when-to-use guidance, no prerequisites (e.g., whether the caller must be a conversation participant), and no mention of alternatives if the conversation is inaccessible. An agent must infer all routing decisions from the tool name alone.

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