Skip to main content
Glama

Extract schedule events

extract_schedule_events
Read-only

Extracts dated events from pasted syllabus text, giving each dated line a title, type, date, and optional times while returning undated lines separately.

Instructions

Extract dated events from pasted syllabus text. Each line that names a date becomes one event, with a title, a type, a date and optional times. Inputs: text (the pasted syllabus or course schedule, one event per line), course (a course name or code to put on every event), year (the year to use when a date has no year) and term_start (the first day of the term, so a line such as Week 5: Midterm becomes an event). Titles are read from the words around the date, and each event is marked as an assignment, exam, quiz, lab, reading, class or other. Any line that has no date is returned in undated_lines instead of being dropped silently. The answer ends with a next step hint that points to build_ics when the events should become a calendar. When no line names a date, the count is 0 and the next step tells the student how to fix the pasted text. Example prompt: "Turn this syllabus into calendar events: Assignment 1 due Sep 15, Midterm exam October 20 at 10:00."

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": {
      "text": "<text>"
    },
    "name": "extract_schedule_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe pasted syllabus or course schedule. Put one event on each line, with a date on the line.
yearNoThe year to use when a date has no year. Defaults to the current year.
courseNoCourse name or code to put on every event, such as BIO 101.
term_startNoFirst day of the term as YYYY-MM-DD. When set, a line like Week 5: Midterm with no date becomes an event on the first day of week 5, where week 1 starts on this date.

Output Schema

NameRequiredDescriptionDefault
yearYesThe year used for dates that did not name one.
countYesHow many events were found.
eventsYesEvery dated event that was found, in date order.
next_stepYesSuggested next tool call for turning the events into a calendar.
undated_linesYesLines that had no date, kept in the order they appeared so they can be fixed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / term_start
      Added value: +{
      +  "description": "First day of the term as YYYY-MM-DD. When set, a line like Week 5: Midterm with no date becomes an event on the first day of week 5, where week 1 starts on this date.",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses real behavior: undated lines are returned in undated_lines rather than dropped, the count is 0 when nothing parses, and the response ends with a next-step hint. That is meaningful disclosure for a pure-read tool, though it does not discuss size limits or how large syllabi are chunked.

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?

The definition is front-loaded with purpose and the key inputs, then behavior, then an example prompt. It is somewhat long and repeats schema content, but no sentence is outright filler and the ordering is sensible.

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 four-parameter extraction tool with an output schema and read-only annotations, the description covers input format, classification behavior, the undated fallback, and the empty case. Return-value explanation is technically redundant given the output schema, but nothing an agent needs in order to call it correctly is missing.

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%, so the baseline is 3. The description restates each parameter's purpose (text, course, year, term_start) but adds essentially no syntax or edge-case detail beyond what the schema descriptions already say, including the Week 5 example that appears verbatim in the schema.

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 opening sentence names a specific verb and resource ('Extract dated events from pasted syllabus text'), and the description clearly positions the tool upstream of build_ics, so it is distinguishable from the sibling calendar-assembly tools.

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 states the input context (pasted syllabus or course schedule, one event per line) and names the follow-on tool, build_ics, when the events should become a calendar. It stops short of an explicit 'do not use this if...' exclusion, but the intended trigger is unambiguous.

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