Skip to main content
Glama

daily_chipotle_limit_guard

Monitor and manage Chipotle consumption to promote healthier eating habits by tracking weekly visits and meal variety.

Instructions

Protects users from excessive Chipotle consumption. A wellness tool for the burrito-dependent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
times_this_weekYesHow many times you've eaten Chipotle this week
times_todayNoHow many times today
last_non_chipotle_mealNoWhat was your last meal that wasn't Chipotle?unknown

Implementation Reference

  • The implementation of the `daily_chipotle_limit_guard` tool, which assesses Chipotle consumption and provides recommendations based on frequency.
      "daily_chipotle_limit_guard",
      "Protects users from excessive Chipotle consumption. A wellness tool for the burrito-dependent.",
      {
        times_this_week: z.number().min(0).describe("How many times you've eaten Chipotle this week"),
        times_today: z.number().min(0).default(0).describe("How many times today"),
        last_non_chipotle_meal: z
          .string()
          .default("unknown")
          .describe("What was your last meal that wasn't Chipotle?"),
      },
      async ({ times_this_week, times_today, last_non_chipotle_meal }) => {
        let severity, message, recommendation;
    
        if (times_today >= 3) {
          severity = "INTERVENTION_REQUIRED";
          message = "This is no longer a diet. This is a lifestyle. And it's concerning.";
          recommendation = "Please call a friend. Or a nutritionist. Or both.";
        } else if (times_this_week >= 7) {
          severity = "CRITICAL";
          message = `You have eaten Chipotle ${times_this_week} times this week. Your blood is 40% cilantro lime rice.`;
          recommendation = "Try vegetables that are not inside a burrito.";
        } else if (times_this_week >= 5) {
          severity = "WARNING";
          message = `${times_this_week} visits this week. You're on a first-name basis with the line cook.`;
          recommendation = "Consider a day off. Your gut microbiome is filing a union grievance.";
        } else if (times_this_week >= 3) {
          severity = "ADVISORY";
          message = `${times_this_week} visits. Approaching the weekly recommended Chipotle intake.`;
          recommendation = "Still within acceptable limits, but the trend is concerning.";
        } else {
          severity = "NOMINAL";
          message = `Only ${times_this_week} visit(s) this week. Those are rookie numbers.`;
          recommendation = "You could eat more Chipotle. Just saying.";
        }
    
        const lastMealNote =
          last_non_chipotle_meal === "unknown"
            ? "You cannot remember your last non-Chipotle meal. This is a red flag."
            : `Last non-Chipotle meal: "${last_non_chipotle_meal}". At least you remember.`;
    
        const lines = [
          "# Chipotle Consumption Monitor",
          "",
          "```",
          "  Daily Limit Guardian v1.0",
          "  =========================",
          `  This Week:     ${times_this_week} visit(s)`,
          `  Today:         ${times_today} visit(s)`,
          `  Status:        ${severity}`,
          "```",
          "",
          `**Assessment:** ${message}`,
          "",
          `**Recommendation:** ${recommendation}`,
          "",
          `*${lastMealNote}*`,
          "",
          ...(times_this_week >= 7
            ? ["> At this point, Chipotle should be offering you equity."]
            : []),
          ...(times_today >= 2
            ? ["> Multiple Chipotle visits in one day is a cry for help wrapped in a tortilla."]
            : []),
        ];
    
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Protects' vaguely suggests a warning or advisory function but fails to specify the mechanism (Does it return a boolean? A warning message? Block subsequent orders?) or disclose side effects, auth requirements, or what constitutes 'excessive'.

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?

Two sentences with zero waste. The first sentence front-loads the core function ('Protects users'), while the second provides categorical context ('A wellness tool'). Every word earns its place; no repetition of schema details or tautology with the name.

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?

Input parameters are fully documented by the schema (100% coverage), but the description omits crucial information about the tool's output (what constitutes a 'protection' response? Is it a string warning, a boolean, or an action?) Given the lack of output schema and annotations, this gap in behavior specification leaves the tool's effect ambiguous.

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%, establishing a baseline of 3. The description adds valuable semantic context by framing the numeric inputs within a 'wellness' and 'burrito-dependent' narrative, explaining why tracking 'times_this_week' matters (health protection), which helps the agent understand the domain constraints beyond raw parameter types.

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?

The description uses a specific verb ('Protects') and clearly identifies the resource (Chipotle consumption) and scope ('excessive'). It successfully distinguishes this wellness/limiting tool from siblings like 'place_order' or 'build_entree' by emphasizing consumption control rather than acquisition or preparation.

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

Usage Guidelines2/5

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

While the phrase 'burrito-dependent' implies a target user persona, there is no explicit guidance on when to invoke this tool versus alternatives (e.g., 'use before placing an order' or 'use for health tracking'). No 'when-not' exclusions or prerequisite conditions are mentioned.

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