Skip to main content
Glama

Get a UT Dallas section

section_get
Read-onlyIdempotent

Retrieve a UT Dallas section by ID to view term dates, meetings, instruction mode, core flags, syllabus, TAs, and instructors.

Instructions

Get a UTD section by ID: term dates, meetings, instruction mode, core flags, syllabus, TAs and instructors. Use grades_get for grade counts.

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": {
      "section_id": "<section_id>"
    },
    "name": "section_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
section_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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, openWorld), so the description's job is to add what they don't. It does that by summarizing the response payload (meetings, syllabus, TAs, instructors), which matters because no output schema exists. It omits error behavior for invalid IDs and any auth or rate context.

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 short sentences, no filler. The core purpose and return contents are front-loaded, and the sibling redirection is deferred to the end where it belongs as a secondary hint.

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-parameter read tool with rich annotations and no output schema, the definition is close to sufficient because it enumerates the returned fields. Only the ID format and failure behavior remain undescribed, which are minor for a lookup-by-key tool.

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?

One parameter with 0% schema description coverage, so the description carries the burden, but 'by ID' merely restates section_id. It never mentions the 24-character hex format that the schema pattern enforces, so an agent reading only prose could supply a slug or numeric ID. The schema pattern limits the damage, keeping this at a baseline passing score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('UTD section') plus the lookup key (ID), then enumerates exactly what comes back: term dates, meetings, instruction mode, core flags, syllabus, TAs, instructors. That level of specificity makes it clearly distinguishable from section_search, which takes non-ID queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers one explicit routing rule: use grades_get for grade counts, which is precisely the confusion an agent would have since grades relate to a section. It gives no comparable rule for section_search vs section_get, though 'by ID' implicitly signals the selector.

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