Skip to main content
Glama

BetterKids Parent Guide

How to play an activity together

how_to_teach
Read-onlyIdempotent

Get the app's own steps for playing or practising a topic with a child. topic can be an activity id, an area id, a skill or a plain topic such as "jump rope", "doctor", "swimming" or "piano"; optionally add the child's age to see only suitable activities. Returns catalog-backed steps in English and Vietnamese (including the seated, gentler and grown-up versions of movement activities), reps or seconds per band and grown-up tips with sources. Nothing is invented: if the catalog has no match, it says so. Read-only; never send a name.

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>"
    },
    "name": "how_to_teach"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching activities (default 4).
topicYesAn activity id (hero.frog-jumps), an area id (piano), a skill (balance) or a plain topic ("jump rope", "doctor", "twinkle", "swimming"). Never a name.
age_yearsNoChild's age in whole years (1-18). Provide age_years OR age_months, not both. The app's content covers ages 3-9.
age_monthsNoChild's age in months (12-216). Provide age_months OR age_years, not both. The app's content covers 36-119 months (ages 3-9).

Output Schema

NameRequiredDescriptionDefault
bandYes
notesYes
lessonsYes
matched_byYes
parent_tipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, yet the description still adds substantive behavior: output is returned in English and Vietnamese, includes seated/gentler/grown-up variants, reps or seconds per band, and sourced grown-up tips. Most importantly it discloses no-match behavior ('if the catalog has no match, it says so') and a no-invention guarantee, which an agent needs to interpret empty results.

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

Conciseness4/5

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

Front-loaded with the core action, followed by accepted topic forms and the age filter, then return characteristics. Dense but every clause carries information; the parenthetical about seated/gentler/grown-up versions is slightly listy but still informative.

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

Completeness3/5

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

Given the rich annotations, a full input schema and an output schema, the definition covers what an agent needs to call it and to interpret 'no match' and 'never a name' responses. The remaining gap is comparative: nothing tells the agent why to choose this over get_activity or age_guide, which matters with seven siblings.

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 already 100%, so the baseline is 3, but the description adds meaning beyond it: it clarifies that age is a suitability filter rather than a lookup key, and that the topic space spans ids, skills and free text. The 'never a name' rule reinforces the schema's privacy note.

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?

Opens with a specific verb and resource: 'Get the app's own steps for playing or practising a topic with a child.' The catalog-backed, step-by-step framing separates it from list/search-style siblings like list_activities or age_guide, though no sibling is named explicitly, so an agent must infer the boundary rather than being routed.

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?

Gives real usage context: topic accepts an activity id, area id, skill or plain topic, and age is optional 'to see only suitable activities.' It also imposes a hard constraint ('never send a name'). However, it never says when to prefer this over get_activity or age_guide, so the when-not guidance is absent.

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