Skip to main content
Glama

skip_week

Skip a HelloFresh delivery week to avoid receiving and being charged for that week's meal kit box. Specify the week identifier to modify your delivery schedule.

Instructions

Skip a delivery week so you won't receive or be charged for that week's box.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
week_idYesThe week identifier to skip (e.g. '2024-W01')

Implementation Reference

  • The skipWeek method is the core handler that implements the tool logic. It uses Playwright to navigate to the HelloFresh deliveries page, locate the specified week by data attribute, click the skip button, and confirm the skip action if prompted.
    async skipWeek(
      weekId: string
    ): Promise<{ success: boolean; message: string }> {
      await this.ensureLoggedIn();
      const page = this.page!;
    
      await page.goto(`${this.baseUrl}/my-account/deliveries`);
      await page.waitForLoadState("networkidle");
    
      // Find the week and click skip
      const weekEl = page.locator(
        `[data-week="${weekId}"], [data-delivery-id="${weekId}"]`
      );
      if (await weekEl.isVisible({ timeout: 5000 })) {
        const skipBtn = weekEl.locator(
          'button:has-text("Skip"), [data-testid*="skip"]'
        );
        if (await skipBtn.isVisible()) {
          await skipBtn.click();
          await page.waitForLoadState("networkidle");
    
          // Confirm skip if prompted
          const confirmBtn = page.locator(
            'button:has-text("Confirm Skip"), button:has-text("Yes, Skip"), [data-testid*="confirm-skip"]'
          );
          if (await confirmBtn.isVisible({ timeout: 3000 })) {
            await confirmBtn.click();
            await page.waitForLoadState("networkidle");
          }
    
          return { success: true, message: `Successfully skipped week ${weekId}` };
        }
      }
    
      return {
        success: false,
        message: `Could not find or skip week ${weekId}. It may not be available for skipping.`,
      };
    }
  • SkipWeekSchema is a Zod schema that validates the input parameter 'week_id' as a required string, with a description indicating the expected format (e.g., '2024-W01').
    const SkipWeekSchema = z.object({
      week_id: z.string().describe("The week identifier to skip (e.g. '2024-W01')"),
    });
  • src/index.ts:201-215 (registration)
    Tool registration for 'skip_week' that defines the MCP tool metadata including name, description, and inputSchema with a required week_id string property.
    {
      name: "skip_week",
      description:
        "Skip a delivery week so you won't receive or be charged for that week's box.",
      inputSchema: {
        type: "object",
        properties: {
          week_id: {
            type: "string",
            description: "The week identifier to skip (e.g. '2024-W01')",
          },
        },
        required: ["week_id"],
      },
    },
  • The case handler for 'skip_week' that parses incoming arguments using SkipWeekSchema and invokes the hellofresh.skipWeek method with the validated week_id parameter.
    case "skip_week": {
      const params = SkipWeekSchema.parse(args);
      const result = await this.hellofresh.skipWeek(params.week_id);
      return text(result);
    }
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action ('skip') and outcomes (no delivery/charge), but lacks details on permissions, reversibility, side effects, or confirmation processes. This is a mutation tool with significant behavioral gaps.

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?

The description is a single, efficient sentence that front-loads the purpose and outcomes with zero wasted words. It is appropriately sized for a tool with one parameter and clear intent.

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?

Given the tool's complexity (mutation with one parameter), no annotations, and no output schema, the description is minimally adequate. It covers the basic action and result but lacks details on behavioral traits, error handling, or integration with sibling tools, leaving gaps for an agent.

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 description coverage is 100%, so the schema fully documents the 'week_id' parameter. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 clearly states the specific action ('skip a delivery week') and the resource affected ('delivery week'), with explicit outcomes ('won't receive or be charged for that week's box'). It distinguishes from siblings like 'modify_delivery' or 'modify_subscription' by focusing on skipping rather than general modifications.

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?

No guidance is provided on when to use this tool versus alternatives such as 'modify_delivery' or 'modify_subscription', which might offer overlapping functionality. The description implies usage for skipping weeks but lacks explicit context, prerequisites, or exclusions.

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/markswendsen-code/mcp-hellofresh'

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