Skip to main content
Glama

Get a UT Dallas academic calendar

academic_calendar_get
Read-onlyIdempotent

Retrieve UTD academic term dates, registration and drop deadlines, and exam schedules for a specified term to plan key academic deadlines.

Instructions

Get UTD academic term dates, registration/drop deadlines and exams. Term accepts 26F or Fall 2026; omitted uses the upstream current marker.

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

Input Schema

NameRequiredDescriptionDefault
termNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful behavior: omitting term falls back to the upstream current marker. It says nothing about freshness of upstream data, caching, or the shape of the returned calendar, which with annotations covering safety keeps this at a 3.

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 with the primary purpose front-loaded and the parameter guidance second. No filler, no restating of the title or name.

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 single-optional-parameter read tool with no output schema and full annotation coverage, the description supplies what's missing: parameter format and default. Only the returned calendar structure and term-range validity remain unaddressed, which is a minor gap.

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 description coverage is 0% with a single free-form term parameter, so the description must carry the burden — and it does, specifying both accepted forms ('26F' shorthand and 'Fall 2026' long form) plus the omission default. It does not define the valid term range or error behavior for unrecognized terms.

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 opens with a specific verb and resource ('Get UTD academic term dates') and enumerates the content covered: registration/drop deadlines and exams. It is readily distinguishable from the course/section/club/professor siblings, though it does not explicitly name a non-overlapping alternative (none appears to exist for calendar data).

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?

Usage is implied by the content listed (you call it when you need term dates or deadlines), and the default behavior when term is omitted is stated. There is no explicit when-not guidance or pointer to an alternative for related queries, so it stays at minimum-viable.

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