Skip to main content
Glama

get_announcements

Retrieve announcements across all courses or filter by course code, using search and result limits to review notices and updates.

Instructions

Latest announcements across all courses, or for one course if a code is given. Bodies are plain text; use get_announcement for the full text of one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
courseNo
searchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully warns that announcement bodies are plain text and effectively truncated (pointing to get_announcement for full text), which is genuine behavioral insight, but it says nothing about ordering, default result volume, or what happens with large limits.

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 tightly written sentences: scope first, then the body-format caveat and the escape hatch to the sibling. No filler, and the most important information is front-loaded.

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?

An output schema exists, so return values need not be described, and the list-versus-detail distinction is well covered. However, for a three-parameter tool with zero schema coverage and no annotations, the absence of any mention of limit or search leaves a meaningful gap.

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% across three parameters. The description partially compensates by explaining that the course parameter takes a code, but limit and search are entirely undocumented in both schema and description, leaving the agent to guess at search scope and result capping.

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?

The description names a specific verb and resource (announcements) and states the exact scope: all courses by default, a single course when a code is supplied. It explicitly distinguishes itself from the sibling get_announcement, so an agent can route between the list and detail tools without inspecting either 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?

It gives a clear selection rule against the closest alternative: use get_announcement for the full text of a single announcement. It does not say when to use search versus course filtering, or how the three parameters interact, so guidance is solid but not exhaustive.

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