Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get UAB Moodle profile

campus_get_profile
Read-onlyIdempotent

Retrieve the authenticated user's basic profile and available read-only capabilities for a specified academic year.

Instructions

Read the authenticated user's basic profile and the available read-only capabilities for one academic year.

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": {
      "year": "<year>"
    },
    "name": "campus_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

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 and open-world behavior, so the safety profile is covered. The description adds useful context beyond them: the call is implicitly self-scoped (no user parameter) and returns capability information scoped to a single academic year. It still says nothing about result shape or size, which matters since no output schema exists.

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 front-loaded sentence with no filler; the scope qualifier ('one academic year') is placed where it is needed. 'Available read-only capabilities' is slightly abstract phrasing that costs a little clarity but no length.

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 one-parameter read tool whose annotations cover safety and which has no output schema, the definition is mostly adequate: it says who the subject is and what categories of data come back. Gaps remain around the year format and what 'capabilities' actually contains, which an agent cannot resolve from the schema.

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?

The single 'year' parameter has 0% schema description coverage, so the description carries the burden; calling it 'one academic year' usefully hints the value is an academic rather than calendar year, which the bare '^\d{4}-\d{2}$' pattern alone does not convey. It never states the expected format or what happens with a year that has no enrollment data.

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 ('Read') and two concrete resources: the authenticated user's basic profile and the read-only capabilities for an academic year. This clearly separates it from the many content-fetching siblings (grades, assignments, course contents), though it does not name any alternative explicitly.

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 implied rather than stated: it reads the current user's own profile, so an agent can infer this is a self-context call rather than a lookup by user id. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as campus_auth_status.

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