StudioMeyer Academy

academy_lessons

Read-onlyIdempotent

Deprecated compatibility listing of original lessons in one numbered level. (Deprecated alias for academy_legacy_lessons; retained for one version.)

Input Schema

Name	Required	Description	Default
`level`	No
`locale`	No	MCP transport locale; not a service input field.	de
`idempotencyKey`	No	Transport retry key, forwarded as Idempotency-Key.

Output Schema

Name	Required	Description	Default
`errors`	Yes
`result`	Yes
`success`	Yes
`messages`	Yes
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +true
```

addedInput schema / description

Added value: +"Deprecated alias: legacy fields are normalized and strictly validated by Academy."

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Transport retry key, forwarded as Idempotency-Key.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / level / description
```
Removed value: -"Level 1-6"
```

changedInput schema / properties / level / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / locale / default
```
Added value: +"de"
```

changedInput schema / properties / locale / description

Previous value: -"Language. de=German, en=English, es=Spanish. Default en."New value: +"MCP transport locale; not a service input field."

changedInput schema / required

Previous value: -[
-  "level"
-]New value: +[]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "errors": {
+          "maxItems": 0
+        },
+        "result": {
+          "additionalProperties": false,
+          "properties": {
+            "lessons": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "description": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "href": {
+                    "type": "string"
+                  },
+                  "id": {
+                    "pattern": "^lesson:-?\\d+(?:\\.\\d+)?:[\\s\\S]{0,}$",
+                    "type": "string"
+                  },
+                  "level": {
+                    "type": "number"
+                  },
+                  "locale": {
+                    "enum": [
+                      "de",
+                      "en",
+                      "es"
+                    ],
+                    "type": "string"
+                  },
+                  "slug": {
+                    "type": "string"
+                  },
+                  "title": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "level",
+                  "slug",
+                  "locale",
+                  "title",
+                  "description",
+                  "href"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "lessons"
+          ],
+          "type": "object"
+        },
+        "success": {
+          "const": true
+        }
+      }
+    },
+    {
+      "properties": {
+        "errors": {
+          "minItems": 1
+        },
+        "result": {
+          "type": "null"
+        },
+        "success": {
+          "const": false
+        }
+      }
+    }
+  ],
+  "properties": {
+    "errors": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "code": {
+            "type": "number"
+          },
+          "documentation_url": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "hint": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "message": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "slug": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "slug",
+          "message",
+          "hint",
+          "documentation_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "messages": {
+      "type": "array"
+    },
+    "request_id": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "result": {},
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "result",
+    "errors",
+    "messages",
+    "request_id"
+  ],
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's genuine addition is lifecycle information (deprecation, one-version retention); it says nothing about what happens when level is omitted or how results are bounded.

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?

Two tight sentences, deprecation status front-loaded, zero filler. The size is proportionate to a deprecated compatibility shim.

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?

An output schema exists, so return values need no explanation, and the tool is a read-only listing. However, optionality of level and the normalization/validation behavior mentioned only in the schema description leave the description a step short for correct invocation.

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 coverage is 67%: locale and idempotencyKey are documented as transport-only fields in the schema itself. The description's "one numbered level" gives the level parameter meaning, but it never addresses that level is optional (all levels? default level?) — the one semantic gap an agent would actually hit.

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 concrete scope ("listing of original lessons in one numbered level") and immediately identifies itself as a deprecated alias of the sibling academy_legacy_lessons, so an agent can place it against academy_lesson/academy_levels. It stops short of a crisp verb+resource framing because "listing" is nominalized and the deprecation notice overshadows what it actually returns.

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 signals the preferred alternative by naming academy_legacy_lessons and warning that this shim is "retained for one version," which is usable routing guidance. It does not say positively when this tool is still the right call (i.e., legacy clients pinned to the old name).

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

All StudioMeyer Academy 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.