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. For how-to questions, select the relevant feature topic; a matching published video link is included when one exists.

For a request to find, report through, or open the feedback form, use topic=troubleshooting. In-app chat must offer the open_feedback action chip, not print the link (chat links render as plain text). External MCP clients may provide the exact Share feedback link returned. Never claim the form was opened without the user tapping the action.

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, including its subscription link when it has one, 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

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

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.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld=false, so the safety profile is covered. The description goes well beyond that with non-obvious behaviors: closed-book grounding ("answer them from this tool's result, never from memory"), the fact the result carries its own grounding rules, video-link inclusion, the constraint that chat links render as plain text, and the rule never to claim the feedback form was opened without a user tap. This is rich, actionable behavioral context.

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?

Front-loaded with purpose, then routing, then behavioral constraints, and nearly every sentence is operational. It is long and the feedback-form guidance recurs across two paragraphs, so it trades some tightness for completeness rather than being crisply minimal.

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?

An output schema exists, so return values need no explanation, and the description still covers grounding, routing, feedback flow, and pricing reproduction rules. Nothing an agent needs to invoke and correctly use this lookup is missing.

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?

Schema coverage is 100% and the enum already defines each value, but the description adds routing semantics the schema cannot: which topic to pick for a how-to question, for feedback requests, and for pricing, plus the narrowest-area selection heuristic. That is meaningful guidance beyond the enum text.

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 and resource ("Look up customer-facing Wellness Project product knowledge") and immediately scopes the domain with concrete topic categories. An agent can tell it apart from the many list_/log_/show_ data tools without opening the schema, since this is the only knowledge-lookup tool.

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?

Explicit when-to-use coverage (navigation, features, integrations, metrics, logging, permissions/sync, troubleshooting) plus explicit when-NOT and alternative routing: "For recognized exercise names ... use list_exercises rather than guessing." It also maps request types to specific topic values (feedback → troubleshooting, cost → pricing), which is exactly the disambiguation an agent needs.

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