Skip to main content
Glama

learnjcu_api_get

Read-only

Retrieve data from any Blackboard Learn public REST endpoint under /learn/api/public/ by sending a read-only GET request.

Instructions

Read-only escape hatch: GET any Blackboard Learn public REST endpoint under /learn/api/public/.

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": {
      "path": "<path>"
    },
    "name": "learnjcu_api_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYese.g. /learn/api/public/v1/courses/_123_1/contents
paramsNoQuery parameters
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's "read-only" confirmation is largely redundant, though it does add the useful constraint that only paths under /learn/api/public/ are valid. It says nothing about authentication requirements, error behavior for invalid/forbidden paths, or response/pagination shape, which matter for an open-world passthrough tool.

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 the key qualifier ("read-only") and scope (/learn/api/public/) stated up front, with no filler. Slightly terse for a generic passthrough, but nothing is wasted.

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 catch-all tool with a nested params object and no output schema, the definition is minimally viable: the agent knows what to send but not what comes back, how errors surface, or whether pagination is supported. Given the tool's open-ended surface, more behavioral detail would help.

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 description coverage is 100%, so baseline is 3. The description reinforces the path prefix constraint, but adds no syntax or usage detail for the nested params object that the schema does not already convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (GET) and an unbounded resource scope bounded by an explicit path prefix (/learn/api/public/). The phrase "read-only escape hatch" distinguishes it from the curated sibling tools like learnjcu_get_content and learnjcu_list_courses, which cover narrower needs.

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?

"Escape hatch" implies last-resort use when no dedicated endpoint wrapper fits, and "read-only" tells the agent it cannot mutate. However, it never states when NOT to use it or names any sibling as the preferred alternative, so the routing decision is left implicit.

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