Skip to main content
Glama

Bettyapp for Teachers

One lecture clip in full

get_clip
Read-onlyIdempotent

One clip in full, by the clip_id a tool gave ("1234:osmosis", "1234:osmosis:2"), or a lecture's id and a second ("1234@300", the moment starting nearest it, within 90 seconds): everything a clip has in a topic's clip search, and the moment's summary, the questions it answers, its topics and the teacher's first words (a short quotation, not the transcript). A lecture no longer on Bettyapp answers available false, with its course's page and no clip to play. 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": {
      "clip_id": "<clip_id>",
      "age_group": "<age_group>"
    },
    "name": "get_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYesThe clip's id as a tool gave it, or "<lecture id>@<second>".
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

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, yet the description adds substantial behavior: the 90-second nearest-moment fallback, the removed-lecture outcome ('available false, with its course's page and no clip to play'), and the caveat that the teacher's words are 'a short quotation, not the transcript'. It also explains the teaching.role/teaching.depth provenance ('judged_by "ai_transcript_review"; not_judged where none was made'), which an agent could not infer from the 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?

Purpose is front-loaded and nearly every clause carries real information (return fields, edge cases, judgment metadata), but it is delivered as a single dense paragraph of nested parentheticals that is harder to parse than a short field list would be.

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

Completeness5/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 describing the return payload, and it does: an enumerated field list plus the notable degradation case. Nothing an agent needs to call this correctly or interpret the response is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by spelling out three concrete clip_id forms and the '@second' tolerance semantics that the schema only hints at. It says nothing about age_group, though the schema fully documents that enum, so no gap is left.

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?

The description opens with a specific verb+resource and scope ('One clip in full, by the clip_id'), and it explicitly contrasts with the clip-search path ('everything a clip has in a topic's clip search'), which lets an agent separate it 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?

It states the two accepted invocation forms ('1234:osmosis' style ids a tool gave, or '1234@300' lecture+second) and the resolution rule (nearest moment within 90 seconds), which effectively implies the search-then-fetch workflow. It stops short of an explicit 'use search_teaching_clips to find ids first' instruction or a when-not-to-use clause.

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