Skip to main content
Glama
UAB Campus MCP

UAB Campus MCP

by HHBYTe

List UAB Moodle Books

campus_list_books
Read-onlyIdempotent

Read Moodle Book metadata and navigation settings for one course to inspect available book content and structure.

Instructions

Read Moodle Book metadata and navigation settings for one course.

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>"
    },
    "name": "campus_list_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a safe, idempotent, externally interacting read. The description adds the useful constraint that results concern book metadata and navigation settings for one course, but it does not clarify whether chapter or page content is included, how multiple books are returned, or any prerequisites or empty-result 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?

The single sentence is direct, front-loaded, and free of filler. It efficiently communicates the operation, resource, information returned, and course scope.

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?

This is minimally adequate for a simple two-argument read with safety behavior covered by annotations. However, with no output schema and undocumented parameters, the definition leaves uncertainty about year semantics, how to obtain a suitable courseId, and whether book contents or only structural settings are returned.

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?

The phrase "for one course" weakly connects courseId to course selection, but neither required parameter is named or explained in the description. In particular, year is not described as an academic year or otherwise related to the query, so the prose does little to compensate for the schema's 0% description coverage.

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 gives a specific verb, resource, and result scope: reading Moodle Book metadata and navigation settings for one course. It does not explicitly distinguish this from broader siblings such as course-content or resource listings.

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?

The single-course scope provides clear usage context, and the metadata/navigation focus indicates what kind of information to seek here. There are no exclusions or guidance about when a broader course-content tool or a page-retrieval tool would be more appropriate.

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