Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

Get one UAB Moodle page

campus_get_page
Read-onlyIdempotent

Read the title, description, and instructional content of a specific Moodle Page activity in a UAB Campus Virtual course by providing its year, course ID, and page ID.

Instructions

Read the title, description, and instructional content of one Moodle Page activity.

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>",
      "courseId": "<courseId>",
      "pageId": "<pageId>"
    },
    "name": "campus_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
pageIdYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only that title, description, and instructional content are returned, which is modest added value; it says nothing about authentication needs, error behavior for invalid pageId, or content size.

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 returned fields are listed before the resource type. It is efficient, though it is arguably too terse given the three undocumented required parameters.

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 simple single-record read with no output schema, the description conveys the essential purpose and the main returned fields. However, it omits all parameter meaning and any hint about the 'year' scoping model, which is the least self-evident part of this tool's contract.

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 carries the full burden for three required parameters, yet it mentions none of year, courseId, or pageId. It does not clarify that 'year' is an academic-period identifier (e.g. 2024-25) or how courseId and pageId relate, leaving the agent to infer semantics purely from names and a regex pattern.

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 uses a specific verb ('Read') plus a precisely scoped resource ('the title, description, and instructional content of one Moodle Page activity'), which lets an agent distinguish it from content-listing or file-download siblings. It stops short of naming any sibling explicitly, so differentiation relies on the reader knowing Moodle's 'Page' activity type.

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 statement of when to use this versus campus_get_course_module, campus_get_course_contents, or campus_download_resource, nor any prerequisite such as needing a valid course/year pair. The singular 'one Page activity' implies usage but gives no exclusions or selection criteria.

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