Skip to main content
Glama

Search UT Dallas courses

course_search
Read-onlyIdempotent

Find UT Dallas courses by exact subject prefix, course number, catalog year, school, or class level; subject prefix is required and results return one paginated upstream page per call.

Instructions

Find UTD courses by exact subject prefix, number, catalog year, school or class level. Prefix required; one upstream page per call.

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": {
      "subject_prefix": "<subject_prefix>"
    },
    "name": "course_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
schoolNo
class_levelNo
catalog_yearNo
course_numberNo
subject_prefixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds one useful operational fact — results come one upstream page at a time, implying cursor paging and multiple calls for broad queries — but says nothing about result caps, ordering, or error behavior for an unknown prefix.

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?

Two short, front-loaded sentences with essentially no filler. The constraint sentence is well placed after the capability sentence, though the phrase 'one upstream page per call' is terse enough to be slightly ambiguous.

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

Completeness3/5

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

For a seven-parameter, output-schema-less search tool, the description gives adequate coverage of the filtering story but not of pagination mechanics or what a result record contains. An agent would need to guess at limit/cursor interaction.

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 description coverage is 0%, so the description carries real weight: it names five of the seven parameters and clarifies that subject_prefix is an exact match and mandatory. It leaves limit and cursor unexplained beyond the vague paging hint, so two parameters remain semantically opaque.

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?

States a specific verb (Find) and resource (UTD courses) plus the filter axes: subject prefix, number, catalog year, school, class level. It is distinguishable from course_get-style lookups by being a filtered search, though it does not name any sibling to contrast against.

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?

'Prefix required' is an explicit precondition and 'one upstream page per call' implies paging, but there is no guidance on when to use this versus course_get, section_search, or professor_search, and no note on how to combine filters.

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