Skip to main content
Glama

BetterKids Parent Guide

Get one BetterKids activity

get_activity
Read-onlyIdempotent

Get everything the catalog says about one activity by id: titles in English and Vietnamese, age bands, minutes, the app's step-by-step wording, reps or seconds per age band where the app defines them, and the area's grown-up tips with their sources. Use ids returned by list_activities. Read-only and free of personal data.

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": {
      "id": "<id>"
    },
    "name": "get_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesActivity id from list_activities, for example hero.frog-jumps or piano-song.hot-cross-buns.

Output Schema

NameRequiredDescriptionDefault
notesYes
activityYes
parent_tipsYes
area_summaryYes

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, destructiveHint=false and openWorldHint=false, so safety is covered structurally; the description still adds that the payload is 'free of personal data', a privacy trait not encoded in any annotation. It does not describe not-found behavior, which is the main remaining behavioral gap.

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?

Opens with the outcome ('Get everything the catalog says about one activity') before the field inventory, and closes with the safety line, so it is front-loaded and purposeful. The middle field list is dense but each item describes a distinct returned value rather than padding.

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 a single documented parameter, full annotations, and an output schema in place, the definition covers what an agent needs to select and call it correctly. The only omission is failure/empty-result behavior for an id that does not exist.

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 coverage is 100% and the id property already documents its source ('Activity id from list_activities'), format examples, pattern, and length, so the description adds little parameter meaning beyond restating the id concept. Baseline 3 applies when the schema carries the semantics.

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?

States a specific retrieval verb, the singular resource ('one activity'), and its key ('by id'), then enumerates the content returned: bilingual titles, age bands, minutes, step-by-step wording, reps/seconds, and grown-up tips with sources. That enumeration lets an agent distinguish it immediately from list_activities, which only enumerates.

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?

'Use ids returned by list_activities' tells the agent the required provenance of the id and names the sibling that produces it, which is a clear usage path. It stops short of saying what to do when a detail is not needed or how to handle an unknown id, so it is strong but not complete.

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