Skip to main content
Glama

Get UT Dallas grade distributions

grades_get
Read-onlyIdempotent

Retrieve UT Dallas historical grade counts by course, instructor, term, or section type, with exact ID/name filters and pagination. Use for grade distribution counts, not GPA.

Instructions

UTD grade counts by ID (overall only) or exact course/instructor filters; overall, term, or term+section-type. Historical counts, not GPA.

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

Input Schema

NameRequiredDescriptionDefault
byNooverall
limitNo
termsNo
cursorNo
course_idNo
last_nameNo
first_nameNo
section_idNo
professor_idNo
course_numberNo
section_numberNo
subject_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/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 bar is lower. The description does add non-obvious behavior: results are historical counts rather than GPA, and ID-based lookups only support the overall grouping. It says nothing about pagination via cursor, the default limit, or the shape of the returned counts.

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?

A single dense sentence with no filler and the most important qualifier ('overall only', 'not GPA') front-loaded. The semicolon-and-parenthetical packing is efficient, though it edges toward telegraphic at the cost of readability.

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

Completeness2/5

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

With 12 parameters, zero schema coverage, and no output schema, this description is far too thin for the tool's complexity. It omits valid filter combinations, defaults, pagination behavior, and what a grade-count record contains, so an agent must guess at most of the surface.

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 description coverage is 0% across 12 parameters, so the description carries the full burden and largely does not. It clarifies the 'by' grouping modes and that IDs mean course/instructor/section identifiers, but leaves terms, limit, cursor, section_number, subject_prefix, and the name fields entirely unexplained, including which filters are mutually exclusive.

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 names the resource precisely (UTD grade counts) and disambiguates it from a nearby concept with 'Historical counts, not GPA.' The verb is implied rather than stated, and the parenthetical 'overall only' is compact to the point of being cryptic, but an agent can still tell what it returns and how it differs from course_get/section_get.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus siblings, nor any instruction to resolve a course_id or professor_id via course_search/professor_search first. The only directional hint is the input-combination note ('by ID (overall only) or exact course/instructor filters'), which is a constraint rather than a when-to-use rule.

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