Skip to main content
Glama

BetterKids Parent Guide

Find BetterKids activities for an age

list_activities
Read-onlyIdempotent

Find BetterKids activities that fit a child's age, a skill and the minutes you have. Searches the app's real content catalog (232 activities across 14 areas: Hero Training, Leo's Piano, Nature Explorer, World Explorer, Little Swimmer, Little Dojo, Jobs, Car Explorer, math, mazes, coding and English words). Send age_years OR age_months (the app covers ages 3-9), optionally skill, area, minutes (the most minutes one go may take) and needs_grown_up. Each result has an id, English and Vietnamese titles, age bands, skill tags, typical minutes (with whether it is computed, stated by the app or an estimate), a one-line how-to and whether the app's notes ask a grown-up to be nearby. Read-only, no account, no network calls. Never include a child's name or any personal detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoFilter by app area, for example piano, nature, hero-training, maze.
limitNoMaximum number of results (default 20).
skillNoFilter by skill tag (see list_topics for the list).
offsetNoSkip this many results, for paging.
minutesNoOnly activities that take at most this many minutes per go.
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).
needs_grown_upNotrue = only activities where the app's notes ask a grown-up to be nearby; false = only those that do not.

Output Schema

NameRequiredDescriptionDefault
bandYesThe age band used for filtering, or null when no age was sent.
notesYes
offsetYes
returnedYes
activitiesYes
total_matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description partly restates that ('Read-only, no account, no network calls'). Beyond annotations it adds genuinely new context: the catalog is the app's real content (not generated), it states the 232/14 corpus size, and it imposes a privacy constraint ('Never include a child's name or any personal detail') that an agent would otherwise not know.

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?

It is front-loaded with purpose and keeps everything in one dense, purposeful paragraph. The long parenthetical enumerations of areas and result fields add bulk that borders on verbose, but each still serves matching, so nothing is clearly wasted.

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?

Eight optional parameters with full schema coverage, annotations carrying the safety profile, and an output schema mean the definition is comfortably complete for calling the tool. It arguably over-describes the result fields (id, bilingual titles, minute provenance) despite the output schema already covering them, but that is redundancy rather than a gap.

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%, so the schema already explains every parameter, including the age-range and OR-exclusivity rules. The description largely mirrors those rules and only marginally extends them ('minutes (the most minutes one go may take)' is a near-duplicate of the schema text), so the 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?

The description opens with a specific verb and resource ('Find BetterKids activities') and states the selection axes (age, skill, available minutes). It also scopes the corpus concretely ('232 activities across 14 areas'), which lets an agent tell this catalog-search tool apart from get_activity or suggest_daily_plan without opening a schema.

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 calling guidance ('Send age_years OR age_months... optionally skill, area, minutes and needs_grown_up'), which is really parameter usage rather than tool-selection guidance. It never names a sibling or states when not to use this tool — e.g., that list_topics supplies the skill vocabulary or that get_activity fetches a single item — so the routing is only implied.

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