Skip to main content
Glama

Bettyapp for Teachers

The topics to teach before a topic and after it

get_topic_pathway
Read-onlyIdempotent

For a topic, the topics recommended before it (recommended_before), those that come next (next), and related topics, each with its best clip judged to teach it, or a fallback moment with its reason. The order comes from how courses teach the topics: a suggestion, not a rule, and only where courses agree; a topic may have none. Useful for planning a sequence of lessons or a review: "what should my class know before the chain rule". Each clip has its clip_id, lecture, start_seconds, suggested_end_seconds, curriculum place, play_url, classroom_share_url, credit line and licence note. teaching.role (teaches, uses or mentions) and teaching.depth (0, named only, to 3, a thorough treatment) say how an AI review of the transcript judged the moment (judged_by "ai_transcript_review"; not_judged where none was made).

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": {
      "topic": "<topic>",
      "age_group": "<age_group>"
    },
    "name": "get_topic_pathway"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic's name, for example "chain rule" or "osmosis".
age_groupYesThe age group of the students the class is for: child (under 13), teen (13 to 17) or adult (18 and over). Bettyapp gives clips from lectures that suit the age.
education_levelNoThe class's Level: elementary (Elementary (K–5)), middle_school (Middle School (6–8)), high_school (High School (9–12)), university_year1 (Year 1 University), university_upper (Upper Year University), graduate (Graduate & Professional). A clip at this Level comes first among clips alike; without it, every Level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the bar is lower; the description nevertheless adds real behavioral context: the ordering is a suggestion rather than a rule, is derived only where courses agree, and may be empty for a topic. It also discloses provenance of the teaching metadata (judged_by 'ai_transcript_review', not_judged where no review exists), which is meaningful confidence information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads the return shape well, but the body is a dense run of long nested sentences, and the enumeration of nine clip fields (clip_id, lecture, start_seconds, play_url, credit line, licence note, etc.) is heavy filler given how much of it is predictable metadata. A reader must work through three sprawling sentences to reach the teaching.role/depth explanation.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so thoroughly, including fallback objects and the meaning of teaching.depth 0–3. Combined with schema-documented parameters and annotations covering safety, the only missing element is guidance on when to choose this over sibling tools.

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% and both enums (age_group, education_level) are documented in the schema, including how education_level reorders clips. The description adds essentially nothing about parameters beyond 'For a topic', 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?

The description names the resource (a topic) and states precisely what is returned: topics recommended before it, topics that come next, and related topics, each paired with a best clip or a fallback moment. That is a distinct verb+result shape that separates it from siblings like get_clip or search_teaching_clips, though no sibling is named explicitly.

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?

It gives a concrete usage context — planning a lesson sequence or a review — with a worked example ('what should my class know before the chain rule'). It does not state when to prefer search_teaching_clips or find_by_curriculum instead, so there are no explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources