Wellness Project

update_cycle

Idempotent

Update an existing period record. Use to correct dates, add a missing end date, or clear an end date (resume).

Common uses:

"my period ended on the 9th not the 8th" → update ended_on
"actually my period started the 2nd not the 3rd" → update started_on
"I'm still on my period" → reopen: true to clear ended_on and mark it active

SELECTOR — pass id if known, or date (the period's start date, or any date that falls within it) to resolve it. Exactly one required. If date matches more than one record, the call errors with candidate IDs to retry with.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Record ID. Alternative to date.
`date`	No	Alternative to id: a date (YYYY-MM-DD) that identifies the period — its start date, or any day within it. Resolves only when exactly one record matches.
`reopen`	No	true clears ended_on and marks the period active again.
`ended_on`	No	Updated end date. Format: YYYY-MM-DD.
`started_on`	No	Updated start date. Format: YYYY-MM-DD. Optional.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Human-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / ended_on / description

Previous value: -"Updated end date. Format: YYYY-MM-DD. Pass null to clear (mark active). Optional."New value: +"Updated end date. Format: YYYY-MM-DD."

addedInput schema / properties / ended_on / nullMeansClear
```
Added value: +true
```

addedInput schema / properties / reopen

Added value: +{
+  "description": "true clears ended_on and marks the period active again.",
+  "type": "boolean"
+}

Changed3 schema fields changedSep 7, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "Alternative to id: a date (YYYY-MM-DD) that identifies the period — its start date, or any day within it. Resolves only when exactly one record matches.",
+  "type": "string"
+}

changedInput schema / properties / id / description

Previous value: -"Record ID from list_cycle. Required."New value: +"Record ID. Alternative to date."

removedInput schema / required
```
Removed value: -[
-  "id"
-]
```

First observedAug 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses real behavioral details: reopen clears ended_on and marks the period active, the date selector resolves any day within the period, exactly one selector is required, and multiple matches produce an error with candidate IDs. These are meaningful operational traits not present in 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.

Conciseness5/5

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

The description is efficiently organized into purpose, common-use examples, and selector rules. Every sentence carries information, the examples are compact, and the critical selector constraint is placed at the end as a distinct section. No filler or redundant restatement.

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?

For a tool with five parameters, an output schema, and a nontrivial selector ambiguity, the description covers everything needed to call it correctly: what it does, which fields map to which intents, how to resolve the record, and the failure mode for ambiguous dates. The presence of an output schema means return values do not need explanation.

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?

Although schema coverage is 100% and each parameter has its own description, the tool description adds significant meaning: id and date are mutually exclusive selectors, date can be a start date or any day within the period, and the examples map natural-language requests to specific parameters (ended_on, started_on, reopen). This goes well beyond the schema.

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?

The description opens with a specific verb and resource: 'Update an existing period record,' then enumerates the concrete actions it supports (correct dates, add a missing end date, clear an end date/resume). The word 'existing' implicitly distinguishes it from log_cycle, and 'update' separates it from delete_cycle, so an agent can tell them apart.

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?

The description clearly states when to use the tool ('Use to correct dates, add a missing end date, or clear an end date') and gives realistic user-intent examples. It does not explicitly name alternatives like log_cycle or delete_cycle or state when not to use it, so it stops one step short of full exclusion guidance.

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

All Wellness Project 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.