Nestling

List nappies

list_nappies

Read-onlyIdempotent

List a baby's nappy (diaper) changes within a time range, each marked Wet, Dirty or Both. Use this for nappies across several days. For one day's totals, prefer get_day_summary.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	Yes	End of the range. 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.
`start`	Yes	Start of the range. 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.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Array of records
`totalResults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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 / end / description

Previous value: -"End: 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: +"End of the range. 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."

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

changedInput schema / properties / start / description

Previous value: -"Start: 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: +"Start of the range. 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."

addedInput schema / properties / start / maxLength
```
Added value: +100
```
addedInput schema / properties / start / 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"
+}

First observedMay 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that each record is classified as Wet, Dirty or Both, but says nothing about pagination, ordering, or limits beyond the annotations.

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 tightly written sentences with the scoping rule front-loaded and the alternative routing second. No filler, though it is very short and could carry slightly more context at no cost.

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?

With an output schema present, return-value explanation is unnecessary, and annotations plus a fully documented schema cover parameters and safety. For a simple filtered-list tool the description is complete.

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% – all four parameters, including the flexible time formats for start/end and the timezone fallback, are documented in the schema. The description adds no syntax or format guidance beyond what the schema already provides, so baseline 3 applies.

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 (List) and resource (a baby's nappy changes) plus scope (within a time range) and the value domain (Wet, Dirty or Both). It clearly differentiates itself from the sibling get_day_summary, which covers single-day totals.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('across several days') and names the alternative tool plus its selecting condition ('For one day's totals, prefer get_day_summary'). Nothing is left to inference.

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?