Skip to main content
Glama

find_matching_indexes

Read-onlyIdempotent

Find NTU course indexes matching day, time, lesson, and teaching-week rules while avoiding supplied timetable clashes.

Instructions

Find indexes matching day/time/lesson/week rules and avoiding supplied timetable clashes.

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": {
      "course_code": "<course_code>",
      "academic_year": "<academic_year>",
      "semester": "<semester>"
    },
    "name": "find_matching_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
semesterYes
constraintsNo
course_codeYes
academic_yearYes
against_sessionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds that the tool avoids supplied timetable clashes and matches day/time/lesson/week rules, which is useful behavioral context, but it does not explain how constraints interact, how uncertainty is handled, or what volume of results to expect.

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 definition is a single, front-loaded sentence with no redundant or filler language. Every clause contributes to understanding what the tool searches for and what it avoids.

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?

With an output schema available and rich nested schema definitions for TimeSlot, TimeWindow, SearchConstraints, and SessionRequirement, the description need not explain return values or every nested field. The one-sentence summary is broadly complete for a constrained search tool, though it leaves usage and required-parameter semantics to inference.

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?

Top-level schema description coverage is low, so the description must compensate. It loosely maps to constraints ('day/time/lesson/week rules') and against_sessions ('supplied timetable clashes'), but it does not explain the required course_code, academic_year, and semester parameters or the detailed semantics of the nested constraint fields.

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 gives a specific verb and resource: 'Find indexes,' and states the filtering criteria as 'day/time/lesson/week rules' and 'avoiding supplied timetable clashes.' It clearly describes a constrained search operation, but it does not explicitly distinguish itself from siblings such as get_course_indexes or compare_indexes.

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: call this when you need indexes that satisfy schedule constraints and avoid clashes. However, there is no explicit when-to-use versus when-not-to-use guidance, and no alternative sibling is named.

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