Skip to main content
Glama

BetterKids Parent Guide

Privacy and safety facts about BetterKids

safety_facts
Read-onlyIdempotent

What a parent usually asks before installing: ads, the grown-up gate, accounts, which data leaves the device, analytics, device permissions, AI usage, contact with others and physical safety. Each statement says which platforms it covers and lists the repo files it was verified against; a not_claimed list says what is deliberately not promised. 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": "safety_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
as_ofYes
claimsYes
contactYes
not_claimedYes
verified_againstYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 safety behavior is fully covered without the description. The description does add real value beyond that — per-statement platform coverage, the repo files each claim was verified against, and a not_claimed list of deliberately unstated promises — but it omits any size/cost signal for what is presumably a sizeable payload.

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, with the topic inventory and the pre-install framing front-loaded. The long comma-separated topic list is dense but each item is a distinct subject area an agent can match against a parent's question; the second sentence on provenance is slightly heavy but earns its place.

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?

With an output schema present, return values need not be explained, and the annotations carry the safety profile. The description still adds provenance semantics (platform scope, verified-against files, not_claimed) that help an agent interpret and cite the results, leaving little missing for a no-argument read-only tool.

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?

The tool takes zero parameters, so the baseline is 4, and the description usefully confirms 'takes no input' rather than leaving the agent to infer it from an empty schema. Nothing further is needed on this dimension.

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?

States a concrete resource (privacy and safety facts about BetterKids) and enumerates the covered topics — ads, grown-up gate, accounts, data leaving the device, analytics, permissions, AI usage, contact with others, physical safety. That enumeration clearly separates it from siblings like app_info or age_guide, though the verb is implied rather than stated (it never explicitly says 'returns a list of statements').

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?

Frames the use case precisely as 'what a parent usually asks before installing,' which gives an agent a clear trigger condition. It supplies no explicit when-not conditions and never names a sibling tool to prefer instead, so it stops short of full routing guidance.

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