Bettyapp lecture moments

The Subjects and Levels

list_subjects

Read-onlyIdempotent

Every Subject with lectures on Bettyapp, each with its Levels and how many lectures it has, and the Level ladder from Elementary to Graduate & Professional. Use it to find the subject and level values for search_moments, or to tell a student what Bettyapp covers.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`terms`	Yes	The terms of use.
`levels`	Yes
`subjects`	Yes
`attribution`	Yes	How to credit Bettyapp and the lecture's creator. Follow it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "description": "How to credit Bettyapp and the lecture's creator. Follow it.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "levels": {
+      "items": {
+        "properties": {
+          "code": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "lectures": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "code",
+          "name",
+          "lectures"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "subjects": {
+      "items": {
+        "properties": {
+          "courses": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "lectures": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "levels": {
+            "items": {
+              "properties": {
+                "code": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "lectures": {
+                  "type": [
+                    "integer",
+                    "null"
+                  ]
+                },
+                "name": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "url": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "name",
+                "code",
+                "lectures"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "The Subject's page, where it has one.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "slug",
+          "lectures",
+          "levels"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "terms": {
+      "description": "The terms of use.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "attribution",
+    "terms",
+    "subjects",
+    "levels"
+  ],
+  "type": "object"
+}

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine content context by describing exactly what the response contains (subjects, their levels, lecture counts, level ladder) and that it is a static reference listing; it does not mention result size or pagination, but with an output schema present that is a minor gap.

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 sentences, front-loaded with what is returned and followed by when to use it. The first sentence is somewhat dense and stacks multiple payload elements, but nothing is redundant or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, strong annotations, and an output schema covering return shape, the description supplies everything else an agent needs: what the listing contains, why it exists, and which sibling consumes its values. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. The description correctly implies a no-argument, full-catalog call rather than a filtered query.

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-and-resource: it enumerates every Subject with lectures on Bettyapp, each with its Levels and lecture counts, plus the Elementary-to-Graduate level ladder. An agent can immediately distinguish this catalog/listing tool from siblings like get_lecture, get_topic, and search_moments.

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?

Explicitly names two concrete use cases: sourcing subject/level values for search_moments, and answering 'what does Bettyapp cover'. That gives clear routing context, though it stops short of stating when not to use it or naming any other alternative.

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

All Bettyapp lecture moments tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?