Skip to main content
Glama

List announcements

bb_list_announcements
Read-only

Lists course announcements with full message bodies and read status, newest first, to help you review course updates and spot unread items.

Instructions

List course announcements, newest first, with bodies and read state.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, but the description adds real context the annotations lack: sort order (newest first) and that announcement bodies and per-user read state are included. It still says nothing about pagination, default page size, or how `limit` affects results.

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 front-loaded sentence with no filler; the ordering and return-content details earn their place. It is perhaps too terse for the parameter gap, but nothing is redundant.

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?

With no output schema, the description usefully previews the return shape (bodies and read state), which is the main thing an agent needs. However, for a paginated list tool it omits how many results come back by default and how `limit` interacts with ordering, leaving gaps an agent would likely hit on first call.

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?

Schema description coverage is 0%, so the description carries the full burden for the two parameters, yet it never explains that `courseId` scopes the listing or what `limit` does (a 1-100 cap with unspecified default). 'Course announcements' only faintly implies courseId, leaving limit entirely undocumented.

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 ("List course announcements") and adds scope detail: ordering newest-first and payload contents (bodies, read state). It does not explicitly contrast with siblings like bb_create_announcement or bb_delete_announcement, but the read verb makes the distinction clear without opening a schema.

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 mention of prerequisites (courseId requirement or enrollment/access), and no alternative tools named. Usage is only implied by the verb 'List' and the 'course' qualifier.

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