Skip to main content
Glama

Get recent course updates

bb_get_recent_updates
Read-only

Retrieve new or changed course content, announcements, assignments, and grades from recently modified gradebook columns, defaulting to the last seven days; set since or courseId to narrow results.

Instructions

New or changed content, announcements, assignments and grades on recently modified gradebook columns. Default last seven days. Dates, files and links identify latest lectures for bb_get_attachment. Grades on older unchanged columns may be missed.

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": "bb_get_recent_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO date or timestamp; date alone means midnight Asia/Dubai
courseIdNoOmit to check up to 20 available courses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world scope, so the safety profile needs no repetition, and the description instead adds genuinely useful behavior: a default seven-day window and an explicit blind spot ("Grades on older unchanged columns may be missed"). That limitation disclosure is exactly the kind of caveat structured fields cannot carry, though the response shape and result ordering remain unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the content types and default window, but the third clause about bb_get_attachment is confusing, ungrammatical, and interrupts the flow rather than routing the agent. Trimming or rewriting that sentence would make the whole definition substantially clearer.

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?

For a two-parameter, no-required-parameter read tool with no output schema, the definition covers default window and a known data-gap, which is reasonable. It stops short of describing what the results look like (grouped by course? by type? sorted by date?) and the vague attachment sentence creates ambiguity rather than resolving it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the seven-day default for the optional `since` parameter. The course-count cap for omitted `courseId` lives only in the schema, so the description does not fully duplicate it, but the added default is a real semantic contribution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the content types returned (content, announcements, assignments, grades) and the recency scope, which is enough to grasp the gist, but it is written as a noun fragment without a verb and the clause "grades on recently modified gradebook columns" muddies whether the tool is a change feed or a gradebook query. No alternative tool is named for the obvious overlap with bb_get_upcoming_work or bb_get_gradebook, so differentiation is left to inference.

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?

"Default last seven days" gives the implicit default window, but there is no statement of when to choose this over bb_get_upcoming_work, bb_get_gradebook, or bb_get_course_content. The only routing hint, "Dates, files and links identify latest lectures for bb_get_attachment," is garbled and does not tell an agent under what condition to switch tools.

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