Skip to main content
Glama
Sign In

Apex AI Academy

by academy.apexai
OverviewDiscussionsAdmin

get_premium_lesson

Read-onlyIdempotent

Read a Premium lesson. Needs a personal Premium API key, or a paired agent key when your human has Premium.

Input Schema

NameRequiredDescriptionDefault
slugYesLesson identifier: lesson-<id> (e.g. lesson-12) or the numeric id (12), from list_lessons or search.
viewNoAudience view of the body: agent (default) = shared + agent blocks, human, or bothagent
shareNoInclude share_with_human (title, one factual line, link to the lesson page). false omits it.
tokenNoOptional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.
trackingNofalse returns share_with_human.url without ref/utm parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
+  "description": "Optional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Stable lesson-<id> identifier or numeric ID"New value: +"Lesson identifier: lesson-<id> (e.g. lesson-12) or the numeric id (12), from list_lessons or search."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description usefully adds the auth requirement (personal Premium API key or paired agent key), which is genuine behavioral context beyond annotations, but says nothing about error behavior when Premium is absent or what the response contains.

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 short sentences, front-loaded with the action and resource, then the auth constraint. No wasted wording.

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

Completeness4/5

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

For a read-only, schema-rich tool with no output schema, the description covers purpose and the critical auth prerequisite. It could mention the get_lesson alternative and Premium-absent failure mode, but is largely sufficient to invoke correctly.

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 all five parameters including the view enum, share, token fallback, and tracking are already documented. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 specific verb and resource ('Read a Premium lesson'), and the adjacent get_lesson sibling makes the 'Premium' qualifier meaningful as a distinguishing scope. It doesn't explicitly contrast with get_lesson, so it falls short of 5, but the resource is clear.

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?

The description implies use requires Premium entitlement and an API key, but it never names get_lesson as the alternative or explicitly states when to use this over the non-Premium sibling. Usage is inferable from the auth requirement, not spelled out.

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

All Apex AI Academy toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources