Skip to main content
Glama

Bettyapp for Teachers

A course's topics in order, with their codes and clips

find_by_curriculum
Read-onlyIdempotent

One study guide's topics in the course's order: each topic's unit, name, what it covers, its codes in the curriculum (section numbers), and its clips (the guide's own picks), recommended or fallback as in a topic's clip search. The guide is named by its id ("ontario/physics/grade-12"), or by its board and course ("Ontario SPH4U", "England GCSE Biology"). unit, section_code and topic limit it to part of the guide; it answers a page of topics at a time. Several matching guides: it answers candidates with their ids. Typical request: "what does SPH4U cover, with clips". 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": {
      "curriculum": "<curriculum>",
      "age_group": "<age_group>"
    },
    "name": "find_by_curriculum"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of topics, from 1.
unitNoOnly the topics of this unit, by its name or a word of it, for example "Dynamics".
topicNoOnly the topics whose name or description has these words.
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.
curriculumYesThe guide: its id, or its board and course name or code, for example "ontario/physics/grade-12", "Ontario SPH4U" or "Cambridge IGCSE Physics".
max_resultsNoHow many topics a page, 1 to 25.
section_codeNoOnly the topics with this code, or under it: "B2.1", or "4.4" for 4.4.1, 4.4.2 ...
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

A4.2/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world); the description adds behavior the agent cannot get elsewhere: pagination ('a page of topics at a time'), the ambiguity case where multiple guides match and candidates with ids are returned instead of topics, and the meaning of the teaching.role/depth judgements including judged_by 'ai_transcript_review' and 'not_judged'.

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?

Front-loads the resource description usefully, but the remaining text is two long run-on sentences with heavy parenthetical nesting (including a nested quote inside a parenthesis), which slows parsing. The clip-field enumeration earns its place given no output schema, but the phrasing could be tightened.

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 eight parameters and no output schema, the description carries the full burden of return-shape disclosure, and it does list the clip fields and the candidate-response case. The one gap is that age_group, a required parameter that shapes clip selection, is not mentioned in the description at all.

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%, so the schema already explains all eight parameters including the enums and ranges. The description restates the filtering role of unit, section_code and topic and repeats the guide-id example format, adding little beyond what the schema says, so baseline 3 applies.

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: one guide's topics in course order, each with unit, name, coverage, curriculum codes and clips. It also names the scope constraint that separates it from a broad clip search ('recommended or fallback as in a topic's clip search'), so an agent can tell it apart from search_teaching_clips without opening either schema.

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?

Explains the guide-naming forms (id, board+course) and gives a concrete triggering request ('what does SPH4U cover, with clips'), plus narrowing via unit, section_code and topic. It never explicitly excludes a sibling (e.g. when to prefer search_teaching_clips or get_topic_pathway), so guidance is clear but not fully routing.

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