Nestling

Add diary entry

create_diary

Add a diary entry (a free-text note or milestone) to the baby's Nestling diary. Use this only when the user asks to write, note or record something in the diary. 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
`tags`	No	Optional tags (max 50 tags, each max 100 characters)
`text`	Yes	The diary entry text (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 it happened

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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 / tags / description

Previous value: -"Optional tags (max 50 tags, each max 100 chars)"New value: +"Optional tags (max 50 tags, each max 100 characters)"

changedInput schema / properties / text / description

Previous value: -"The diary entry text (max 10,000 chars)"New value: +"The diary entry text (max 10,000 characters)"

changedInput schema / properties / timestamp / description

Previous value: -"When the event 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 it happened"

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"
+}

Changed5 schema fields changedMay 29, 2026
- changedInput schema / properties / tags / description
```
Previous value: -"Optional tags (e.g. ['milestone', 'funny'])"New value: +"Optional tags (max 50 tags, each max 100 chars)"
```
- addedInput schema / properties / tags / items / maxLength
```
Added value: +100
```
- addedInput schema / properties / tags / maxItems
```
Added value: +50
```
- changedInput schema / properties / text / description
```
Previous value: -"The diary entry text"New value: +"The diary entry text (max 10,000 chars)"
```
- addedInput schema / properties / text / maxLength
```
Added value: +10000
```
First observedMay 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false; the description goes further by warning that each call appends a new entry and must not be retried after success, which is actionable context an agent could otherwise miss. It still says nothing about auth/permissions or limits.

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?

Front-loads the purpose, then usage constraint, then retry warning, then timestamp-format rules. Four sentences, each carrying distinct operational information with no repetition of schema text.

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?

A write tool with full annotations and an output schema, so return values need no explanation. Purpose, when-to-use, retry behavior, and the tricky timestamp/timezone semantics are all covered, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds real meaning beyond it: it enumerates the accepted timestamp formats (ISO 8601, relative, day+time, time only, date+time) and explains the timezone fallback for zone-less times, all of which the schema only labels as 'When it happened'.

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 diary entry ... to the baby's Nestling diary') and clarifies the entry type as a free-text note or milestone, which cleanly separates it from list_diary and the other create_* logging tools.

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 when-to-use trigger ('only when the user asks to write, note or record something in the diary') plus an operational guard ('do not retry after success'). It never names a sibling alternative (e.g. list_diary for reads), so 4 rather than 5.

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?