Skip to main content
Glama

post_gym_macro_mode

Configure a nutritionally optimized burrito based on your workout activity and fitness goals to support post-exercise recovery.

Instructions

Automatically configures a nutritionally optimized burrito based on your workout. Gains-as-a-Service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityYesWhat workout did you just do?
goalNoCurrent fitness goalmaintain

Implementation Reference

  • Registration and implementation of the 'post_gym_macro_mode' tool, which takes activity and goal arguments and returns a configured burrito order.
    server.tool(
      "post_gym_macro_mode",
      "Automatically configures a nutritionally optimized burrito based on your workout. Gains-as-a-Service.",
      {
        activity: z
          .enum(["ran_5k", "ran_10k", "lifted_weights", "crossfit", "yoga", "walked_to_fridge", "rest_day"])
          .describe("What workout did you just do?"),
        goal: z
          .enum(["bulk", "cut", "maintain", "survive"])
          .default("maintain")
          .describe("Current fitness goal"),
      },
      async ({ activity, goal }) => {
        const configs = {
          ran_5k: {
            protein: "Chicken", double: false, rice: "Brown Rice", beans: "Black Beans",
            toppings: ["Fajita Veggies", "Fresh Tomato Salsa (Mild)", "Lettuce"],
            note: "Moderate cardio detected. Balanced rebuild protocol activated.",
          },
          ran_10k: {
            protein: "Chicken", double: true, rice: "Brown Rice", beans: "Black Beans",
            toppings: ["Fajita Veggies", "Fresh Tomato Salsa (Mild)"],
            note: "Serious mileage. Double protein authorized. Skip the cheese, you earned it differently.",
          },
          lifted_weights: {
            protein: "Steak", double: true, rice: "White Rice", beans: "Black Beans",
            toppings: ["Cheese", "Fajita Veggies", "Fresh Tomato Salsa (Mild)"],
            note: "Anabolic window is OPEN. Maximum protein deployed.",
          },
          crossfit: {
            protein: "Chicken", double: true, rice: "White Rice", beans: "Pinto Beans",
            toppings: ["Guacamole", "Cheese", "Fajita Veggies", "Lettuce"],
            note: "You probably already told everyone about your WOD. Here's your reward.",
          },
          yoga: {
            protein: "Sofritas", double: false, rice: "Brown Rice", beans: "Black Beans",
            toppings: ["Fajita Veggies", "Lettuce", "Fresh Tomato Salsa (Mild)"],
            note: "Namaste. Your burrito has been spiritually aligned.",
          },
          walked_to_fridge: {
            protein: "Carnitas", double: false, rice: "White Rice", beans: "Pinto Beans",
            toppings: ["Cheese", "Sour Cream", "Guacamole"],
            note: "Cardio is cardio. No judgment. Full indulgence mode.",
          },
          rest_day: {
            protein: "Chicken", double: false, rice: "Brown Rice", beans: "Black Beans",
            toppings: ["Lettuce", "Fresh Tomato Salsa (Mild)"],
            note: "Rest day = discipline day. Minimal toppings. Character building.",
          },
        };
    
        const config = configs[activity];
    
        // Goal adjustments
        let goalNote = "";
        if (goal === "bulk") {
          config.double = true;
          config.toppings.push("Cheese", "Sour Cream");
          config.toppings = [...new Set(config.toppings)];
          goalNote = "BULK MODE: Extra everything. Calories are your friend.";
        } else if (goal === "cut") {
          config.rice = "No Rice";
          config.toppings = config.toppings.filter((t) => !["Cheese", "Sour Cream", "Guacamole"].includes(t));
          goalNote = "CUT MODE: Rice eliminated. Flavor sacrificed at the altar of abs.";
        } else if (goal === "survive") {
          goalNote = "SURVIVAL MODE: Just eat something. Anything. Please.";
        }
    
        const lines = [
          "# Post-Workout Burrito Configuration",
          "",
          `**Activity:** ${activity.replace(/_/g, " ")}`,
          `**Goal:** ${goal}`,
          "",
          "## Optimized Order",
          "",
          `- **Entree:** Bowl (always bowl for macro tracking)`,
          `- **Protein:** ${config.double ? "Double " : ""}${config.protein}`,
          `- **Rice:** ${config.rice}`,
          `- **Beans:** ${config.beans}`,
          `- **Toppings:** ${config.toppings.join(", ")}`,
          "",
          `> ${config.note}`,
          ...(goalNote ? ["", `> ${goalNote}`] : []),
        ];
    
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior2/5

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

No annotations provided, so description carries full burden. States 'automatically configures' but fails to disclose what system state changes occur (creates draft order? saves preference? returns recommendation only?), auth requirements, or side effects.

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?

Extremely brief (two sentences). Front-loaded with functional description first; second sentence ('Gains-as-a-Service') is promotional fluff but doesn't significantly detract from parsability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for simple 2-parameter tool with 100% schema coverage, but ambiguity about relationship to order flow (configuration vs. placement) and no output disclosure leaves gaps given the complex sibling ecosystem.

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

Parameters3/5

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

Schema has 100% description coverage ('What workout did you just do?', 'Current fitness goal'), establishing baseline 3. Description adds conceptual link between workout and nutrition but does not augment parameter syntax, format, or validation details beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb ('configures') and resource ('burrito') with domain context ('based on your workout'). Implicitly distinguishes from generic sibling 'build_entree' by focusing on post-workout nutrition optimization, though explicit differentiation is absent.

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

Usage Guidelines3/5

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

Provides implied usage context (post-gym meals) via 'based on your workout', but lacks explicit when-to-use guidance, prerequisites, or named alternatives among the 13 sibling tools like 'build_entree' or 'customize_order'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YoshiSaurus/mcp-otle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server