Skip to main content
Glama

Get a UT Dallas course

course_get
Read-onlyIdempotent

Retrieve a UT Dallas course by ID to view catalog metadata, description, prerequisite/corequisite tree, and section count. Use course search to find the ID first.

Instructions

Get a UTD course by ID: catalog metadata, description, prerequisite/corequisite tree and section count. Use course_search to find IDs.

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_id": "<course_id>"
    },
    "name": "course_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 without description help. The description adds value by disclosing return contents (prereq tree, section count) but says nothing about behavior on a nonexistent course ID or about response size/latency for deep prerequisite trees.

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 sentences, zero filler, with the payload enumeration front-loaded before the sibling pointer. Every clause carries information the agent needs.

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 no output schema, the description correctly takes on the job of describing what is returned, and it does so concisely. A read-only single-parameter tool needs little more; minor gaps are the missing not-found behavior and the ID format already available in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 single parameter, and it only gestures at it with "by ID." It never states the expected 24-character hex format encoded in the schema pattern, nor that the value must come verbatim from course_search — the phrase "Use course_search to find IDs" only weakly implies provenance.

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 and resource ("Get a UTD course by ID") and enumerates exactly what comes back: catalog metadata, description, prerequisite/corequisite tree and section count. That payload list distinguishes it from course_search, which it names explicitly.

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?

Explicitly routes the agent to course_search when it does not yet have an ID, which is the main usage decision for a by-ID lookup. It stops short of stating exclusions or what to do if the ID is stale/invalid, but the primary alternative is named.

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