Skip to main content
Glama

BetterKids Parent Guide

List BetterKids areas, skills and age bands

list_topics
Read-onlyIdempotent

List every area of the BetterKids app (for example piano, nature, hero-training, maze), the skill tags, the three age bands (3-4, 5-6, 7-9) and how many activities each has, plus the catalog digest. Call this first to learn valid values for the skill and area filters of list_activities. Read-only; takes no input.

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_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
appYes
areasYes
bandsYes
notesYes
skillsYes
catalog_digestYesDigest of the data/ files the snapshot was built from.
total_activitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description reinforces it with "Read-only" and adds the useful input shape fact "takes no input." It also hints at return contents (counts plus catalog digest), which goes beyond the annotations, though the output schema already documents the response. Net: additive but not deeply so.

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?

Two sentences, front-loaded with the resource and its contents, followed by the routing instruction. The parenthetical examples and age-band list are dense but each item is informative; only mild trimming is possible without losing useful payload detail.

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?

For a no-parameter, read-only catalog tool with an output schema present, the description covers purpose, contents, input shape, and its role in the workflow. Nothing an agent needs in order to call it correctly 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?

Zero parameters, so the baseline is 4. The description is consistent with the empty schema and explicitly tells the agent "takes no input," removing any doubt about whether filters can be passed here rather than to list_activities.

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 ("List every area of the BetterKids app") and enumerates the exact payload: areas with concrete examples (piano, nature, hero-training, maze), skill tags, the three named age bands, activity counts per band, and a catalog digest. An agent can distinguish this from list_activities, get_activity, or age_guide without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prescription: "Call this first to learn valid values for the skill and area filters of list_activities." That names the sibling tool, states the ordering, and explains what the output is for, so the agent knows both when to call this and why it precedes the filtered list.

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