Skip to main content
Glama

BetterKids Parent Guide

Suggest a short daily play plan

suggest_daily_plan
Read-onlyIdempotent

Suggest a short play-and-learn plan for one day from the app's catalog: send the child's age in months (36-119 for ages 3-9), up to 8 interests such as "animals" or "piano" (English or Vietnamese) and the minutes available. Returns an ordered list of activities that fit the minutes, with a reason for each; the same inputs always give the same plan and day (1-7) varies it across a week. It starts where the app itself starts the day and flags activities where the app asks a grown-up to be nearby. A suggestion, not a prescription, with no developmental claims. Read-only; interests are matched against the catalog and never echoed or stored. Never send a child's name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "age_months": "<age_months>"
    },
    "name": "suggest_daily_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoDay of the week 1-7. Changes which equally good activities are picked, so a week of plans varies. The same inputs always give the same plan.
minutesNoTotal minutes available (5-120, default 20).
interestsNoUp to 8 short interests such as "animals", "piano", "maze", "cars" (English or Vietnamese). Words that match no area are ignored. Never include names or personal details.
age_monthsYesChild's age in months (12-216); the app's content covers 36-119 months (ages 3-9). Never send a name.

Output Schema

NameRequiredDescriptionDefault
bandYes
planYes
notesYes
grown_up_noteYes
total_minutesYes
matched_interestsYesCatalog topics your interests matched (ids only; your words are not echoed).
requested_minutesYes
ignored_interest_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses determinism tied to `day` variation across a week, that flagged activities are ones where a grown-up should be nearby, that interests are matched and never echoed or stored, and a privacy constraint ("Never send a child's name"). These are behavioral facts an agent cannot recover from readOnlyHint/idempotentHint alone.

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?

Front-loaded with purpose then inputs then return behavior then caveats, which is a sensible order. The semicolon-chained sentences are dense and the return-format detail is somewhat redundant given an output schema exists, but no sentence is filler.

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 4-parameter, read-only recommendation tool with an output schema, the description covers what an agent needs: inputs, determinism, what the returned plan contains, safety flagging, and privacy limits. Nothing material is missing.

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 every parameter, including the day-variation and range semantics. The description restates the supported 36-119 month band and the English-or-Vietnamese interest matching, which is mildly useful but adds little beyond the structured fields.

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?

Opens with a specific verb and resource ("Suggest a short play-and-learn plan for one day from the app's catalog") and immediately scopes it by inputs (age, interests, minutes). An agent can distinguish this from catalog-browsing siblings like list_activities or get_activity 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 Guidelines4/5

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

States the usage context clearly (one day, from the app catalog, sized to available minutes) and adds framing that this is "a suggestion, not a prescription." It does not explicitly name when to prefer a sibling such as list_activities for open-ended browsing, so routing guidance is implied rather than stated.

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