Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Find UAB courses

campus_find_courses
Read-onlyIdempotent

Find a course by name, code, or numeric ID across one or all authenticated academic years. Review each match’s kind—including non-subject spaces—to select the correct course.

Instructions

Resolve a course name, code, or numeric ID across one or every authenticated academic year. Matches include non-subject spaces; check each match's kind.

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": {
      "query": "<query>"
    },
    "name": "campus_find_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds that matches may fall in non-subject spaces and that each match carries a 'kind' the caller should inspect, which is genuinely useful behavioral context, but it says nothing about result limits, ordering, or what an empty result means.

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, front-loaded with the core action, with no filler. The phrasing 'non-subject spaces' and 'kind' is terse to the point of being slightly cryptic for a reader without prior knowledge of the result shape.

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?

For a search-over-heterogeneous-data tool with no output schema, the description covers inputs reasonably but leaves the return contract thin: it hints at a 'kind' discriminator without describing the match object, and it omits limit/pagination behavior. Adequate but with clear gaps for an agent deciding how to consume results.

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?

Schema coverage is 0%, so the description must carry parameter meaning. It does explain that the query accepts a name, code, or numeric ID, and that year can scope to one year or all years if omitted. However, it never mentions the limit parameter (default 10, max 20) or the YYYY-XX year format, so a third of the parameters remain undocumented.

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 states a specific verb and resource: 'Resolve a course name, code, or numeric ID' into courses. The 'name, code, or numeric ID' framing distinguishes it from a plain listing, though it never names campus_list_courses as the alternative, so the sibling boundary is left implicit.

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?

Usage is only implied: 'resolve' suggests lookups where the exact identifier is uncertain, and 'across one or every authenticated academic year' implies the optional year. There is no explicit when-to-use versus when-to-use-list guidance and no statement about what to do when nothing matches.

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