Skip to main content
Glama

Bettyapp for Teachers

A topic at each Level

get_levels
Read-onlyIdempotent

A topic at each Level Bettyapp has a lecture for it, from school to university: one clip a Level, the Levels as the lectures are placed. Useful for an easier or a harder explanation, or for a mixed class. A Level with no lecture is left out; Bettyapp says nothing about a Level it has no lecture at. evidence says whether the clip is recommended (judged to teach) or a fallback. 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_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic's name, for example "photosynthesis".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, non-destructive and closed-world, and the description adds meaningful behavior: Levels without lectures are omitted, evidence distinguishes recommended from fallback, and teaching.role/depth plus judged_by explain AI transcript judgments. It also enumerates returned clip fields, which is useful given there is no output schema.

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 purpose is front-loaded, but the prose is run-on and includes redundant wording such as 'Bettyapp says nothing about a Level it has no lecture at.' The opening is also awkwardly punctuated, and the field enumeration, while useful, is not tightly organized.

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 two-parameter retrieval tool with no output schema, the description supplies return-field names and semantics for evidence and teaching judgments. It still leaves response shape, ordering and level-count expectations implicit, but it is broadly complete for this complexity.

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 100%; topic and age_group are fully documented in the input schema, including the age_group enum meanings. The description does not add parameter-specific syntax or constraints beyond use-case color, so the baseline 3 is appropriate.

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 states that the tool returns a topic's clips at each Level, one clip per Level, from school to university, and names the classroom use. It is specific about the resource and scope, but it never distinguishes this tool from siblings such as get_topic_pathway or search_teaching_clips.

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?

It gives a use context (easier or harder explanation, mixed class) but no explicit when-not or alternative-routing guidance. The agent must infer whether to call this versus get_topic_pathway or search_teaching_clips.

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