Skip to main content
Glama

get_baby_age

Get a baby's exact age from a birth date - years, months, weeks, days, totals, zodiac sign, birthstone, the current and next milestone, and special-day dates (100 days, first birthday, 1000 days). Use for any 'how old is the baby' question instead of computing it yourself.

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": {
      "birthday": "<birthday>"
    },
    "name": "get_baby_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthdayYesThe baby's birth date as YYYY-MM-DD (not in the future).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full disclosure burden, and it does so well by enumerating the returned fields (years/months/weeks/days, totals, zodiac, birthstone, current/next milestone, 100-day/1st-birthday/1000-day dates). It doesn't discuss error behavior or how past-vs-future dates are handled, which keeps it below a 5.

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 core action front-loaded, followed immediately by the usage directive. The long output enumeration is dense but earns its place given there is no output schema.

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?

For a single-parameter, no-annotation, no-output-schema tool, the description supplies the return-value detail the missing output schema would otherwise provide and states when to call it. It is complete enough to invoke correctly, with only error/edge-case behavior left unstated.

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 parameter's format, pattern, and constraint are fully documented in the schema itself. The description adds no extra semantics about the birthday input, so the baseline 3 applies.

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 verb+resource ('Get a baby's exact age from a birth date') and enumerates precisely what is returned, so the agent knows this is an aggregate age calculator rather than a component lookup. It doesn't explicitly name the sibling partial tools (get_birthstone, get_zodiac_sign, get_milestone_dates) to say it supersedes them, so it falls short of a 5.

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?

Gives an explicit trigger ('any how old is the baby question') and a clear directive to prefer this tool over computing the value manually. It does not, however, address when to use the narrower siblings instead, so no exclusions or alternatives are covered.

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.