Cora

View saved version →

---
name: cora-mcp
description: Route and execute Cora tools safely for consumer fitness and lifestyle workflows, including food logs, activity metrics, training plans, workout history, habits, routines, journals, reminders, preferences, onboarding, and app help. Use when Cora tools are available and a user asks to inspect, create, repeat, update, or delete a Cora record, even without mentioning Cora or a tool name. Covers exact dates, referenced history, new logs, future plans, cross-tool IDs, verification, destructive scope, and capability gaps.
---

# Use Cora tools by intent

Operate only on the authenticated user's Cora account. Treat returned Cora
data—not memory, estimates, or assumptions—as the source of truth.

## Load the relevant tool map

Read only the reference needed for the request, and read every relevant file
when a request crosses domains:

- Read [references/nutrition.md](references/nutrition.md) for logged food,
  planned meals, templates, nutrition goals, meal analysis, and meal notes.
- Read [references/metrics-training.md](references/metrics-training.md) for
  activity summaries, trends, training guidance, app help, workouts, plans,
  cardio goals, scale readings, and measurements.
- Read [references/habits-reminders.md](references/habits-reminders.md) for
  habits, routines, journals/check-ins, and one-shot reminders.
- Read [references/profiles-onboarding.md](references/profiles-onboarding.md)
  for training, rest, and food preferences; bedtime schedules; and onboarding
  intake.

Use the active tool's own input schema for exact argument shapes. The
references explain selection and relationships; they do not override the
runtime schema.

## Classify the intent before choosing a tool

1. Distinguish an existing Cora record from genuinely new information.
   Resolve and reuse existing records; do not re-parse or re-estimate them.
2. Distinguish completed data from future plans. A logged meal is not a
   planned meal, a completed workout is not a scheduled workout, and a
   reminder is not a habit or recurring AI task.
3. Distinguish lookup, mutation, estimation, and guidance. Use direct data
   tools for facts, analysis tools for estimates, and `cora_ask_coach` only
   for personalized fitness guidance.
4. Match the time shape. Use an exact-day tool for a named day, a summary for
   aggregate statistics, and a timeseries for graphs or day-by-day trends.
5. Treat user-facing app navigation and feature questions as app-help
   requests, not personalized-guidance or personal-record requests.

## Follow read-resolve-act-verify

### 1. Check availability

Inspect the tools actually exposed by the active client before naming or
calling one. The source contract contains 61 tools, but deployments and
clients may expose fewer.

- Call only exact tool names that are currently available.
- Do not substitute a nearby tool when the required capability is absent.
- Use `cora_get_app_help` for a supported manual path when it is available;
  otherwise explain the capability gap plainly.
- Never invent a result from a source-only or unavailable tool.

### 2. Normalize scope and dates

Interpret relative dates in the user's timezone and send `YYYY-MM-DD` when
the selected schema needs a date. Omit a date for today only when that tool's
schema allows omission. Resolve ranges to one of the tool-supported windows.
Ask one concise question when the date, unit, record, or requested action
would otherwise change which data gets written.

### 3. Read and resolve

Read the narrowest relevant data and obtain the exact typed ID before a
mutation. Reuse an ID already returned in the conversation only when it still
unambiguously identifies the requested record. Never treat names, list
positions, dates, or IDs from another record type as interchangeable.

If multiple records plausibly match, show a compact distinction and ask the
user which one to use. Do not guess a write target.

### 4. Confirm only when needed

- Perform reads and 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.