Skip to main content
Glama

Proactive Parent guidance

Baby and child age guidance

age_guidance
Read-onlyIdempotent

What to expect at one age of a baby or young child (birth to 6 years), for a family in any country (the UK, the US and Türkiye have their own guidance; every other country gets general guidance): the week-by-week guide for the first year, the check-ups and things to do around that age where the region has them, and reading for it. Our own written guidance, with the pages it drew on.

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": {
      "region": "<region>",
      "age": "<age>",
      "unit": "<unit>"
    },
    "name": "age_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesThe child's age, in the unit given (up to 6 years).
unitYesThe unit of the age.
regionYesWhere the family lives and gets care. GB: the United Kingdom. US: the United States. TR: Türkiye. INTL: general guidance for every other country, such as Germany, India or Brazil. Required, with no default, because care differs between countries: guidance is never taken from another region.
languageNoThe language to answer in. If the region's guidance is not written in it, the region's own language is used (GB and US: en; TR: tr; INTL: en, tr, es, fr).
born_at_weekNoOnly for a baby born before 37 weeks of pregnancy: the week they were born. The guide then follows their corrected age, as their care team does, until two years.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, closed-world lookup, so the description's job is to add context — and it does: guidance is the service's own written content with cited source pages, guidance is never borrowed from another region, and for premature babies the guide follows corrected age until two years. What is missing is any sense of response size or shape (single age vs. full timeline), though no output schema exists to cover that 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?

It is compact — effectively two sentences — and front-loads the core scope ('What to expect at one age of a baby or young child'), which is the right ordering. But the first sentence is overloaded with nested parentheticals that interrupt the main clause, and the trailing fragment 'Our own written guidance, with the pages it drew on' is tacked on rather than integrated.

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 five parameters, three enums, fully described schema, and no output schema, the description is nearly sufficient: it conveys scope, the regional isolation rule, the corrected-age exception, and roughly what content comes back. The remaining shortfall is that it never clarifies the relationship to week_guidance or hints at the volume/format of the returned guidance.

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 schema itself already spells out the region enum semantics, the language fallback chain, and the born_at_week corrected-age rule in detail. The description adds only the outer age ceiling ('birth to 6 years') and reinforces regional isolation, which the schema already states. Baseline 3 is appropriate when the schema does this much of the work.

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 names a specific resource — age-based guidance for a child from birth to 6 years — and enumerates what it returns: the week-by-week guide for the first year, region-specific check-ups and activities, and reading material, all sourced from the service's own written guidance. That is well beyond a tautology. It does not, however, differentiate itself from the sibling week_guidance, even though it explicitly claims to cover week-by-week content for the first year, leaving an overlap the agent must resolve on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: the reader infers this is the tool for a single child's age, and the parenthetical explains the region split (UK/US/Türkiye get their own guidance; everyone else gets general guidance). There is no explicit 'use this when... use week_guidance instead when...' routing, and no stated prerequisites, so the agent must guess how it relates to the sibling.

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