Skip to main content
Glama
Sign In
UPC-MCP

UPC-MCP

by dlam12138
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upc_timetable_range

Read-onlyIdempotent

Retrieve all course instances for a bounded natural-date range (max 14 days or 3 teaching weeks), including dates, weekdays, periods, location and teacher; fails if any required week is incomplete.

Instructions

Read one bounded natural-date range with every course instance.

The range is capped at 14 days and three teaching weeks. Each item has a real date, ISO weekday, periods, time, location/teacher and a stable instance_id; counts.total/returned/complete describe the whole range. Any required week failure fails the call instead of returning a partial empty timetable.

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": {
      "year": "<year>",
      "term": "<term>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "upc_timetable_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes学期列表中的学期编号，例如 1。
yearYes学期列表中的学年，例如 2026-2027。
end_dateYes自然日期终点，含当天；范围最多 14 天/3 个教学周。
start_dateYes自然日期起点，显式 YYYY-MM-DD（Asia/Shanghai）。
session_refNoself

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real, non-obvious behavior: partial results are never returned, any required-week failure aborts the whole call, and completeness is exposed via counts.total/returned/complete. That is meaningful context beyond the structured fields.

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?

Front-loaded with the operation and scope, followed by limits and return shape; every sentence carries content. Slight redundancy with the schema in restating the 14-day/3-week cap, but that constraint is the tool's defining risk and is worth repeating.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing returns and does so: item fields (date, ISO weekday, periods, time, location/teacher, instance_id) plus the counts.* summary. Combined with the stated failure semantics, an agent has enough to call it safely and interpret results.

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 80%, so start_date/end_date/term/year are already documented in the schema in the same terms. The description reinforces the 14-day cap and adds the meaning of the returned instance_id, but says nothing about session_ref ('self') or about the interaction between calendar range and teaching-week boundaries.

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 ('Read one bounded natural-date range with every course instance'), which is clearly more precise than a bare name. It implicitly distinguishes itself from the week-scoped sibling by insisting on a bounded multi-day range, though it never names upc_timetable_week or upc_timetable_terms as alternatives.

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?

It states the hard operational constraint (max 14 natural days / 3 teaching weeks) and the all-or-nothing failure rule, which helps an agent decide whether a request is valid. However, there is no explicit guidance on when to choose this over the single-week tool, so the selection logic is only implied.

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

Deploy Server

Other Tools