Skip to main content
Glama

Nestling

by com.nestling-app.mcp
OverviewDiscussionsAdmin

List diary entries

list_diary
Read-onlyIdempotent

List a baby's diary entries (free-text notes and milestones) within a time range. Use this when the user asks what they wrote, or about notes and milestones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd 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.
startYesStart 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.
babyIdYesThe baby's ID from list_babies
timezoneNoThe 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
NameRequiredDescriptionDefault
dataYesArray of records
totalResultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds that results are scoped to a time range and contain notes/milestones, but says nothing about ordering, pagination, or empty-result behavior.

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?

Two sentences, zero filler, with the what (list diary entries in a time range) front-loaded ahead of the when-to-use clause.

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?

An output schema exists, so return-value detail is unnecessary, and all four parameters are fully described in the schema. The definition covers what and when, though it omits ordering/volume expectations an agent might want for a listing tool.

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%, with start/end formats, babyId provenance, and timezone fallback all documented in the schema itself. The description only restates that a time range is required, adding no meaning beyond structured fields. 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) plus resource (a baby's diary entries) and characterizes the content as free-text notes and milestones within a time range. This clearly distinguishes it from siblings such as list_feeds, list_nappies, and list_sleep.

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 explicit trigger conditions: when the user asks what they wrote, or about notes and milestones. It does not name competing alternatives (e.g., get_day_summary or show_day for a broader day view), so it stops short of full routing guidance.

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

All Nestling toolsInspect
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