Skip to main content
Glama

get_announcement

Retrieve the full text of a specific course announcement using the course and announcement ID, so you can read or reference its complete details.

Instructions

Full text of one announcement.

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": "<course>",
      "announcement_id": "<announcement_id>"
    },
    "name": "get_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
announcement_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about read-only nature, permission requirements, behavior when the ID does not exist or is from another course, or truncation of the "full text".

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 zero filler. It is efficient, though the terseness is part of the under-specification problem rather than a virtue on its own.

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?

With no annotations, no output schema, and two entirely undocumented parameters, the definition leaves too much unspecified for a tool that takes identifiers of ambiguous type. Safe-call details such as whether course is an ID and what happens on missing announcements are absent.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds nothing about the two required parameters. It does not clarify whether "course" expects a course ID, code, or name, nor whether announcement_id is scoped per course, leaving the agent without the information it needs to construct a valid call.

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?

"Full text of one announcement" names a specific resource and scope, and the singular "one announcement" implicitly contrasts with the sibling get_announcements (plural listing). The retrieval verb is only implied by the tool name, not stated in the description, so it falls just short of 5.

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?

No when-to-use guidance, no mention of get_announcements as the alternative for listing, and no prerequisites such as needing a valid course/announcement ID first. The agent must infer selection from the plural/singular distinction alone.

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