Nestling

Log nappy

create_nappy

Add a nappy (diaper) change to the baby's Nestling log: Wet, Dirty, or Both. Use this only when the user asks to log or record a nappy change. Each call adds a new entry, so do not retry after success. Accepts ISO 8601 ("2026-05-07T20:00:00Z"), relative ("2 hours ago", "now"), day and time ("today 3pm", "yesterday 8:30pm"), time only ("3pm"), or date and time ("2026-05-07 8pm"). Times without a zone use the timezone argument.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	Nappy type
`notes`	No	Optional notes (max 10,000 characters)
`babyId`	Yes	The baby's ID from list_babies
`timezone`	No	The user's IANA time zone, such as "Europe/London". When left out, the host's location hint is used if it sends one, else UTC.
`timestamp`	Yes	When the nappy was changed

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`totalResults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 5, 2026

changedInput schema / properties / babyId / description

Previous value: -"The baby's UUID"New value: +"The baby's ID from list_babies"

changedInput schema / properties / notes / description

Previous value: -"Optional notes (max 10,000 chars)"New value: +"Optional notes (max 10,000 characters)"

changedInput schema / properties / timestamp / description

Previous value: -"When the nappy change happened: Date/time — accepts ISO 8601 (\"2026-05-07T20:00:00Z\"), relative (\"2 hours ago\", \"now\"), day+time (\"today 3pm\", \"yesterday 8:30pm\"), time-only (\"3pm\"), or date+time (\"2026-05-07 8pm\")"New value: +"When the nappy was changed"

addedInput schema / properties / timestamp / maxLength
```
Added value: +100
```
addedInput schema / properties / timestamp / minLength
```
Added value: +1
```

addedInput schema / properties / timezone

Added value: +{
+  "description": "The user's IANA time zone, such as \"Europe/London\". When left out, the host's location hint is used if it sends one, else UTC.",
+  "maxLength": 64,
+  "type": "string"
+}

addedOutput schema / properties / data / properties / at

Added value: +{
+  "description": "When the entry happened, ISO 8601 UTC",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / localTime

Added value: +{
+  "description": "The same time in the time zone used, with the zone name",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / timezone

Added value: +{
+  "description": "Time zone used to read the times given",
+  "type": "string"
+}

Changed2 schema fields changedMay 29, 2026
- changedInput schema / properties / notes / description
```
Previous value: -"Optional notes"New value: +"Optional notes (max 10,000 chars)"
```
- addedInput schema / properties / notes / maxLength
```
Added value: +10000
```
First observedMay 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare non-idempotency, and the description adds the actionable consequence ('Each call adds a new entry, so do not retry after success') plus the timezone fallback chain when the zone is omitted. It does not disclose permissions, rate limits, or failure modes, but for an append-only log tool with annotation coverage this is solid added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each carrying distinct load: what it creates, when to call it (with the retry warning), and how timestamps are parsed. The scoping sentence is front-loaded before the format detail.

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?

An output schema exists so return values need not be explained, and the description covers the remaining gaps an agent needs: exact use condition, non-idempotent retry behavior, and timestamp/timezone interpretation for all five parameters.

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?

Schema coverage is 100%, so the baseline is 3, but the description materially extends the thin schema text for timestamp ('When the nappy was changed') by enumerating accepted formats — ISO 8601, relative, day+time, time-only, date+time — and clarifying the timezone fallback rule.

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 verb and resource ('Add a nappy (diaper) change to the baby's Nestling log') and enumerates the domain values (Wet, Dirty, Both), which cleanly separates it from create_feed, create_sleep, and create_diary without opening any 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?

Explicitly scopes invocation: 'Use this only when the user asks to log or record a nappy change,' and adds a retry constraint ('do not retry after success'). It gives a clear condition for use but never names an alternative sibling (e.g. list_nappies or open_quick_log) for the read/edit cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nestling tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?