Skip to main content
Glama

Skip one day of a repeating task

skip_occurrence
Idempotent

Skip a repeating task on one day only, e.g. "no gym this Monday". The rest of the series stays. Can be reverted with undo_last_change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "templateId": "<templateId>",
      "dayKey": "<dayKey>"
    },
    "name": "skip_occurrence"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayKeyYesThe day to skip.
templateIdYesRepeating task id (repeatingTaskId / id from list_repeating_tasks, get_week or search_tasks). The id of one of its occurrences also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description explains the exact effect: only one occurrence is skipped and the rest of the series remains intact. It also discloses reversibility via undo_last_change, which is useful behavioral context. It does not describe permissions or response behavior, but the annotations already cover safety and idempotency hints.

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 three short sentences, front-loaded with the core action and scope. Every sentence adds value: the example clarifies the use case, the series-retention note distinguishes behavior, and the undo note covers recovery.

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

Completeness4/5

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

For a two-parameter mutation tool with full schema coverage and useful annotations, the description is nearly complete: it conveys scope, effect on the series, and reversibility. It does not document return behavior, but no output schema exists and the tool is simple enough that this is a minor gap.

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%, and the schema already explains dayKey and templateId, including that an occurrence id may be used. The description adds a helpful example of a skipped day but does not add parameter-level meaning beyond the schema.

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 states a specific verb and resource: "Skip a repeating task on one day only." It immediately clarifies the scope with "The rest of the series stays," which distinguishes it from stopping or updating the entire repeating series.

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

Usage Guidelines4/5

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

The description gives a clear use case ("no gym this Monday") and distinguishes one-day skipping from affecting the rest of the series. It also names undo_last_change for reverting, but it does not explicitly state when not to use this tool or contrast it with sibling alternatives such as stop_repeating_task or update_repeating_task.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources