Skip to main content
Glama

Search UT Dallas professors

professor_search
Read-onlyIdempotent

Find UTD professors by exact, case-sensitive first and/or last name. Requires at least one name and returns paginated matches without fuzzy matching or capitalization retries.

Instructions

Find UTD professors by exact, case-sensitive first and/or last name. At least one name required; no fuzzy matching or capitalization retries.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
last_nameNo
first_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavioral rules: exact case-sensitive matching and no retry loop. It notably supplies the 'at least one name required' constraint that the schema omits (required is empty), which is high-value disclosure. It says nothing about result ordering or pagination behavior.

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, zero waste, with the matching rule front-loaded and the constraint second. Nothing is redundant with the annotations or title.

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?

The critical matching semantics and the implicit required-parameter rule are covered, which is the main correctness risk. However, with no output schema and no pagination explanation, the agent is not told what a result looks like or how to page through results via cursor.

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%, so the description must carry all parameter meaning. It clarifies first_name/last_name matching semantics (exact, case-sensitive, either or both), but limit and cursor are completely unmentioned — the agent gets no explanation that cursor is an opaque pagination token or how limit interacts with the 1–20 cap.

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 ('Find') and resource ('UTD professors') plus the matching key (exact, case-sensitive first and/or last name). It is clearly a search rather than a fetch-by-ID, so it is distinguishable from professor_get in practice, though no sibling is named 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?

Gives a concrete usage constraint: at least one name is required, and there is no fuzzy matching or capitalization retry, which tells the agent to stop after one failed attempt rather than guessing name variants. It does not route explicitly to professor_get for ID-based lookups, so it stops short of full when/when-not guidance.

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