Skip to main content
Glama

Search UT Dallas sections

section_search
Read-onlyIdempotent

List UTD Trends sections by exact course (subject prefix and number) and/or professor (first and last name), optionally filtered by term.

Instructions

List UTD Trends sections by exact course (prefix+number) and/or professor (first+last name), optionally term (26S/26U/26F). Coverage may lag.

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

Input Schema

NameRequiredDescriptionDefault
termNo
limitNo
cursorNo
last_nameNo
first_nameNo
course_numberNo
subject_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description then earns credit for a genuine caveat the annotations do not carry: 'Coverage may lag.' However, it says nothing about the paginated nature of the call (limit/cursor exist in the schema) or how results are ordered.

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 dense sentences, no filler, with the primary action and exact-match constraints front-loaded and the caveat trailing. Every clause carries information an agent needs.

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?

With no output schema and 0% param coverage across seven parameters, the description must do more work than it does. The listing/pagination contract (limit default 10, max 25, cursor) is the largest gap for a list tool. Safety and scoping are adequately handled.

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 0%, so the description must carry the load; it does explain the pairing constraints for subject_prefix/course_number, first_name/last_name, and the term format (26S/26U/26F), which is real added meaning. But limit and cursor — two of the seven parameters — are never mentioned, and it never says all filters are optional so the tool can enumerate broadly.

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 and resource ("List UTD Trends sections") plus the exact filter dimensions it accepts. The 'exact course (prefix+number)' and 'professor (first+last name)' qualifiers distinguish it from a free-text search, and 'List' contrasts implicitly with sibling section_get. It stops short of naming which sibling to use for fuzzy/keyword lookups.

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?

"and/or" plus "optionally term" makes the combination rules clear, so an agent can infer broad usage. But there is no explicit when-to-use/when-not guidance versus course_search or professor_search, and no statement about what happens with zero filters. Usage is implied rather than directed.

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