Skip to main content
Glama

Get a UT Dallas professor

professor_get
Read-onlyIdempotent

Retrieve a UT Dallas professor by 24-character ID to view directory contacts, office location and hours, profile details, and bounded section references without expanding courses.

Instructions

Get a UTD professor by ID: directory contacts, office, office hours, profile and bounded section references. Does not expand courses.

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": {
      "professor_id": "<professor_id>"
    },
    "name": "professor_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
professor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description's real addition is return-shape information — results are bounded and courses are not expanded — which is useful, but it says nothing about behavior on a missing/invalid ID or about payload limits beyond the word "bounded."

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 sentences with the core purpose and scope limit front-loaded and nothing padding it out. "Bounded section references" is slightly jargon-heavy but earns its place by signaling truncated payloads.

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 usefully enumerates the fields a caller receives, and the annotations cover the safety profile, so the definition is nearly self-sufficient for a simple single-record read. The remaining gap is ID provenance and not-found behavior.

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%, with only a regex pattern on professor_id doing the documenting, so the description is expected to compensate and largely does not. "By ID" restates the parameter name; it never says where the ID comes from (e.g., professor_search results) or what a valid value looks like.

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 professor") and enumerates the returned facets: directory contacts, office, office hours, profile, and bounded section references. The "by ID" phrasing plus "Does not expand courses" separates it cleanly from professor_search and course_get without opening either schema.

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?

The scope note "Does not expand courses" and "by ID" imply this is a single-record lookup, which hints at when to use it, but no alternative is named and no prerequisite is stated. An agent must infer that professor_search is the right tool for name/keyword lookups.

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