Skip to main content
Glama

BetterKids Parent Guide

What each age band gets in BetterKids

age_guide
Read-onlyIdempotent

Describe what each age band (3-4, 5-6, 7-9) gets in the app, from the real content: for example the daily activity for ages 3-4, repeat blocks in Code Quest from 5-6, one-way roads and traffic lights in mazes at 7-9. Returns counts of activities per area and sourced statements. These are facts about the app's content, not developmental milestones or advice. Send band, age_years or age_months, or nothing for all three. Read-only.

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": "age_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoOne age band (3-4, 5-6 or 7-9). Omit to get all three.
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
bandsYes
notesYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses the return contents ('counts of activities per area and sourced statements') and asserts the data is sourced from real app content rather than general knowledge, which an agent needs for trustworthy citation.

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 the core purpose, then coverage examples, then return shape, then input selection, then a scope caveat. The content examples (Code Quest repeat blocks, one-way roads in mazes) are illustrative and earn their place by showing what 'real content' means, but the dependency and schema restatements make it slightly longer than strictly necessary.

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?

An output schema exists, so return values need not be fully spelled out, yet the description still summarizes them usefully. For a zero-required-parameter, three-parameter lookup tool it is essentially complete; the only gap is that it accepts ages up to 18 without saying what is returned when the age falls outside the 3-9 content range.

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 documents band, age_years and age_months including mutual exclusivity and valid ranges. The description only restates the same selection rule ('band, age_years or age_months, or nothing for all three') and adds no new meaning such as how an age outside 3-9 would be resolved.

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?

The description states a specific verb and resource: describe what each named age band (3-4, 5-6, 7-9) gets in the app, with concrete examples of the kind of content covered. It also draws a boundary against an adjacent category ('facts about the app's content, not developmental milestones or advice'), which helps separate it from advice-oriented siblings like how_to_teach, though no sibling is named directly.

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 gives clear selection guidance for inputs ('Send band, age_years or age_months, or nothing for all three') and a scope boundary excluding milestone/advice requests. It stops short of explicitly routing to an alternative tool when the user actually wants teaching advice, so it is clear context rather than full when/when-not/alternatives coverage.

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