Baby Routine MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BABY_ROUTINE_API_URL | No | Where the API lives (default: http://localhost:8010) | http://localhost:8010 |
| BABY_ROUTINE_USER_ID | No | Firebase uid this server acts for | |
| BABY_ROUTINE_ID_TOKEN | No | Alternative: a Firebase ID token | |
| BABY_ROUTINE_TRANSPORT | No | stdio (local client) or streamable-http (remote) | stdio |
| BABY_ROUTINE_SERVICE_TOKEN | No | Must match MCP_SERVICE_TOKEN in the API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_resourcesA | List the record types this baby app stores and the JSON fields each accepts. Call it before writing a record whose fields you are unsure about. Resources: babies, feedings, sleep_sessions, diaper_changes, baths, growth_measurements, observations, medications, medication_doses, medication_purchases, clothing_items, attachments. |
| log_recordB | Create one record.
|
| update_recordB | Update fields of an existing record, e.g. marking a clothing item as too_small. |
| delete_recordC | Delete a record the mother asked to remove. |
| search_recordsB | Read records of one resource, filtered by date range (YYYY-MM-DD) and exact fields. Example: search_records("clothing_items", filters={"size": "S", "category": "body"}) answers "which bodies size S do I have?". |
| medication_reportC | Cost and adherence per medication in a period. Returns how much was spent, how many units were bought, how many doses were given, on how many days, and the average doses per day. |
| routine_reportC | Per-day counts and period averages for feedings, diapers, sleep and baths. |
| today_overviewC | Today's snapshot: age, counts so far, medication adherence and active alerts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: CRUD operations (log/update/delete/search), schema discovery, and specialized reports. However, routine_report and today_overview both return daily counts for feedings/diapers/sleep, so an agent might need to read descriptions carefully to pick the right one.
The majority of tools follow a verb_noun pattern (describe_resources, log_record, update_record, delete_record, search_records), but the reporting tools break this with noun_noun names (routine_report, medication_report, today_overview). The convention is otherwise consistent and readable.
Eight tools is well-scoped for a baby routine tracker: generic CRUD via log/update/delete/search, a schema explorer, and three reporting/overview tools. Each tool serves a distinct need without redundancy.
The generic log/update/delete/search surface covers all twelve resource types listed by describe_resources, so no record type is a dead end. Reporting covers routine events, medications, and a daily snapshot, and missing analytics like growth charts are not core to the stated purpose.