Skip to main content
Glama

BetterKids Parent Guide

Where to get BetterKids

app_info
Read-onlyIdempotent

Where to get the BetterKids app and what is available today: iPhone and iPad (App Store, 1.0.6), Mac (Mac App Store, 1.0.1 live), Android (NOT in the public Google Play: a direct APK from GitHub Releases) and the web app. Links are given only for what is publicly available, with version numbers and the date they were checked. Also returns languages, the pricing model in one sentence (no prices) and support and privacy links. 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": "app_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoWhich platform to describe (default all).all

Output Schema

NameRequiredDescriptionDefault
appYes
as_ofYesDate the availability and version numbers were checked.
notesYes
supportYes
platformsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral value: links are only emitted for publicly available channels, version numbers carry a check date (freshness semantics), the Android build is explicitly an APK from GitHub Releases rather than Google Play, and no prices are returned. That is meaningful context beyond the structured fields.

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?

One dense, front-loaded paragraph that leads with the core answer and then lists coverage. The trailing 'Read-only.' duplicates the readOnlyHint annotation and earns nothing, and the parenthetical version numbers add bulk, but overall there is little waste.

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 spelled out, and the description still summarizes them at a high level while covering the tricky edge case (Android distribution). The only omission is any hint that results can be scoped via the platform parameter, which leaves a small gap for a tool with a filtering input.

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% and the single platform parameter has an enum plus default already documented in the schema, so the baseline applies. The description lists the platforms that exist, which reinforces the enum values, but never explains that the parameter filters the response to one platform — no added meaning beyond the schema.

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 names a specific resource (BetterKids app availability per platform) and enumerates exactly what comes back: store links, version numbers, check date, languages, a one-sentence pricing model, and support/privacy links. It is unmistakably distinct from the content-oriented siblings (list_activities, age_guide, safety_facts), which do not deal with distribution or download channels.

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?

The scope statement ('where to get the app and what is available today') makes the trigger condition clear, and the Android caveat tells the agent when a non-store answer is the correct one. It stops short of an explicit 'use this when the user asks about downloads/versions' instruction or naming an alternative, so it falls just below the top band.

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