Skip to main content
Glama

Wellness Project

by ai.wellnessproject
OverviewDiscussionsAdmin

get_app_guide_section

Read-onlyIdempotent

Look up customer-facing Wellness Project product knowledge. Use it for app navigation, visible features, integrations, metric meanings, logging methods, permissions/sync questions, or troubleshooting.

Wellness Project-specific answers are closed-book: answer them from this tool's result, never from memory. The result states its own grounding rules.

Use wearables for supported integrations, basic connection requirements, broad data coverage, and explicitly documented provider limitations. Use metrics for user-facing metric meanings. Use sync_details only for permissions, history depth, missing history, and detailed sync behavior. Use troubleshooting only when the user reports unexpected behavior or asks how to recover.

For recognized exercise names or whether an exercise is in the app's exercise library, use list_exercises rather than guessing or expecting the app guide to enumerate exercises.

For cost, price, Free vs Pro, Founding Member, upgrading, or the 3-analysis limit, use topic=pricing. Reproduce exactly one returned pricing message verbatim, include the supplied subscription link, and add no other pricing detail. The app attaches its own upgrade button to that message when one applies; never type out a button, chip, link markup, or call-to-action of your own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesChoose the narrowest relevant area. pages_dashboard = Dashboard, Me, Settings, AI Assistants. pages_training = Fitness, workouts, running, cycling, heart, recovery. pages_nutrition = nutrition, hydration, caffeine, sleep, body, wellbeing, labs. personas = AI specialists. logging = ways to log/correct data. photos = meal photos, labels, barcodes. wearables = integrations, connection requirements, known provider limits. metrics = user-facing metric meanings. goals = goals/targets. challenges = friend challenges. privacy = account controls/policy links. sync_details = permissions, history, missing-data behavior. troubleshooting = unexpected behavior/recovery. pricing = approved pricing copy.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesHuman-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Choose the narrowest relevant area. pages_dashboard = Dashboard, Me, Settings, AI Assistants. pages_training = Fitness, workouts, running, heart, recovery. pages_nutrition = nutrition, hydration, sleep, body, wellbeing, labs. personas = AI specialists. logging = ways to log/correct data. photos = meal photos, labels, barcodes. wearables = integrations, connection requirements, known provider limits. metrics = user-facing metric meanings. goals = goals/targets. challenges = friend challenges. privacy = account controls/policy links. sync_details = permissions, history, missing-data behavior. troubleshooting = unexpected behavior/recovery. pricing = approved pricing copy."New value: +"Choose the narrowest relevant area. pages_dashboard = Dashboard, Me, Settings, AI Assistants. pages_training = Fitness, workouts, running, cycling, heart, recovery. pages_nutrition = nutrition, hydration, caffeine, sleep, body, wellbeing, labs. personas = AI specialists. logging = ways to log/correct data. photos = meal photos, labels, barcodes. wearables = integrations, connection requirements, known provider limits. metrics = user-facing metric meanings. goals = goals/targets. challenges = friend challenges. privacy = account controls/policy links. sync_details = permissions, history, missing-data behavior. troubleshooting = unexpected behavior/recovery. pricing = approved pricing copy."
  2. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Choose one general help area. pages_dashboard = Dashboard, Me, Settings, Fit Score, Insights. pages_training = Fitness, Train, PRs, running, heart, recovery, injuries. pages_nutrition = Fuel, Nutrition, sleep, body, wellbeing, cycle, labs. personas = AI specialists. logging = ways to log or edit data. photos = meal photos, labels, barcodes. wearables = connected health sources and AI assistants. goals = goals and standard targets. challenges = friend challenges. privacy = account controls and links to posted policies only. troubleshooting = common navigation and recovery steps. pricing = the two approved product pricing messages plus the subscription link."New value: +"Choose the narrowest relevant area. pages_dashboard = Dashboard, Me, Settings, AI Assistants. pages_training = Fitness, workouts, running, heart, recovery. pages_nutrition = nutrition, hydration, sleep, body, wellbeing, labs. personas = AI specialists. logging = ways to log/correct data. photos = meal photos, labels, barcodes. wearables = integrations, connection requirements, known provider limits. metrics = user-facing metric meanings. goals = goals/targets. challenges = friend challenges. privacy = account controls/policy links. sync_details = permissions, history, missing-data behavior. troubleshooting = unexpected behavior/recovery. pricing = approved pricing copy."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "pages_dashboard",
-  "pages_training",
-  "pages_nutrition",
-  "personas",
-  "logging",
-  "photos",
-  "wearables",
-  "goals",
-  "challenges",
-  "privacy",
-  "troubleshooting",
-  "pricing"
-]New value: +[
+  "pages_dashboard",
+  "pages_training",
+  "pages_nutrition",
+  "personas",
+  "logging",
+  "photos",
+  "wearables",
+  "metrics",
+  "goals",
+  "challenges",
+  "privacy",
+  "sync_details",
+  "troubleshooting",
+  "pricing"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Which section of the app guide to load. Pages are split by area — pages_dashboard = Dashboard / Fit Score / Insights / Me / Trophy Case / Crew Blog / About / Settings (+devices/notifications/specialists/photos/chatgpt/delete-account) / rating prompt; pages_training = Fitness (PRs/steps/running) / Train (On Deck, Plan with Jamie, Muscle Fatigue Heat Map) / Heart / Recovery / Injuries; pages_nutrition = Nutrition / Sleep / Body / Wellbeing / Cycle / Labs / Challenges / Goals. Personas = the AI specialist roster. Logging = how each data type is logged. Photos = photo meal scanning. Wearables = Fitbit/Oura/Apple Health/Health Connect/ChatGPT/MCP integrations. Goals = formal goals + standard targets + lifecycle. Challenges = friend challenges (steps/PR/rep). Privacy = data export, deletion, privacy policy. Troubleshooting = common how-do-I and why-isnt-X questions."New value: +"Choose one general help area. pages_dashboard = Dashboard, Me, Settings, Fit Score, Insights. pages_training = Fitness, Train, PRs, running, heart, recovery, injuries. pages_nutrition = Fuel, Nutrition, sleep, body, wellbeing, cycle, labs. personas = AI specialists. logging = ways to log or edit data. photos = meal photos, labels, barcodes. wearables = connected health sources and AI assistants. goals = goals and standard targets. challenges = friend challenges. privacy = account controls and links to posted policies only. troubleshooting = common navigation and recovery steps. pricing = the two approved product pricing messages plus the subscription link."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "pages_dashboard",
-  "pages_training",
-  "pages_nutrition",
-  "personas",
-  "logging",
-  "photos",
-  "wearables",
-  "goals",
-  "challenges",
-  "privacy",
-  "troubleshooting"
-]New value: +[
+  "pages_dashboard",
+  "pages_training",
+  "pages_nutrition",
+  "personas",
+  "logging",
+  "photos",
+  "wearables",
+  "goals",
+  "challenges",
+  "privacy",
+  "troubleshooting",
+  "pricing"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only and idempotent safety, and the description adds behavioral context annotations cannot express: the closed-book grounding requirement ('answer them from this tool's result, never from memory'), the verbatim-reproduction rule for pricing messages, and the prohibition on typing out buttons, chips, or link markup. The note that the app attaches its own upgrade button also informs expected output handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The core purpose is front-loaded in the first sentence and the text is organized into distinct sections (purpose, grounding rule, tool routing, sibling routing, pricing behavior) with no fluff. It is long, and the wearables/metrics/sync_details/troubleshooting routing prose partly duplicates the schema's enum descriptions, so it is not maximally concise — but every paragraph earns its place given the routing complexity.

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 single-parameter lookup tool with an output schema, full enum documentation, and safety annotations, the description is complete: it covers purpose, when to use internal topics vs sibling tools, grounding behavior, and the special pricing output format. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% with detailed per-enum descriptions, so the schema carries the semantic weight. The description adds modest value by mapping cost/price/Free-vs-Pro/Founding-Member/3-analysis-limit queries to topic=pricing — details beyond the schema's terse 'approved pricing copy' — but otherwise reinforces rather than extends the schema's enum meanings.

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 — 'Look up customer-facing Wellness Project product knowledge' — and enumerates concrete use cases (app navigation, visible features, integrations, metric meanings, logging methods, permissions/sync, troubleshooting). It differentiates from siblings by expressly naming list_exercises for exercise-name lookups and pricing for cost questions, so an agent can distinguish it without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Routing guidance is explicit and actionable: within the tool it tells which topic to use for which need (wearables vs metrics vs sync_details vs troubleshooting), and outside it names list_exercises as the alternative for exercise names. It even states a positive selection rule ('Use troubleshooting only when the user reports unexpected behavior') and a negative one ('never from memory').

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

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