Skip to main content
Glama

List calendar

bb_list_calendar
Read-only

Retrieve calendar events and assignment deadlines within a specified ISO 8601 date range, filtered by course or personal events, so you can track upcoming graded work and your own scheduled items.

Instructions

List calendar items and deadlines in a date range (ISO 8601). Includes graded activity due dates and your personal events.

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_list_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO start, e.g. 2026-11-01T00:00:00Z
untilNoISO end, e.g. 2026-12-01T00:00:00Z
courseIdNoFilter to one course
onlyPersonalNoOnly events you created

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this is a read-only, closed-world operation, so the safety profile is covered. The description adds useful scope details about ISO 8601 date ranges and the types of calendar items returned, but it does not disclose ordering, pagination behavior, or how the personal-events inclusion interacts with filters.

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?

The description is two tight sentences with no filler. The core scope and inclusion details are front-loaded, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with four optional, fully documented parameters and read-only annotations, the description covers the essential scope and included content. It could be stronger with notes on result ordering or pagination, but no output schema is present and the core behavior is clear.

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

Parameters3/5

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

Schema coverage is 100%, with descriptions for since, until, courseId, and onlyPersonal, so the schema already provides parameter meaning. The description reinforces ISO 8601 date formatting and mentions personal events, but adds little semantic detail beyond what the schema states.

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 uses a specific verb and resource: 'List calendar items and deadlines in a date range,' and clarifies that graded activity due dates and personal events are included. It is distinguishable from calendar CRUD tools, but it does not explicitly differentiate from sibling list tools such as bb_list_assignments or bb_list_assessments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The date-range scope implies when this tool is appropriate for calendar views, and the inclusion of graded activity due dates and personal events gives useful context. However, it does not explicitly state when to choose this over related list tools or mention any exclusions or alternatives.

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