Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

Skip one period

schedule_skip

Skip one billing period without halting the entire schedule. Prevents an invoice for that occurrence while keeping all other periods billed normally, and reports the unbilled amount with undo instructions.

Instructions

Skip a single occurrence of a schedule without pausing it: no invoice is ever created for that period, and every other period bills as normal. Returns the amount that will not be billed and how to undo it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSchedule id, or a client name
undoNoRemove a previous skip so the period becomes due again. Works only on a period that has not been invoiced. Default false
periodYesThe occurrence date to skip, YYYY-MM-DD, exactly as it appears in schedule_upcoming or forecast. This is the answer to "pause this client for October": schedule_pause stops the whole schedule and a resumed schedule still back-bills the periods it missed, whereas a skipped period is closed for good

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key side effects: no invoice is created for the skipped period, every other period bills normally, and it returns the amount not billed and how to undo. It does not explicitly describe the undo behavior as an action of this tool, but the schema covers that.

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 no wasted words. The core action, effect, and return value are stated efficiently and front-loaded.

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?

The description plus rich schema covers the main decision (skip vs. pause), the invoicing effect, and the return value. It omits explicit mention of the undo parameter as a call path, but the schema documents it. Sufficiently complete for a three-parameter tool.

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 all parameters are already documented in the input schema. The tool-level description adds minimal parameter-specific meaning beyond the 'single occurrence' context, so baseline 3 is appropriate.

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: 'Skip a single occurrence of a schedule.' It explicitly distinguishes from pausing and references the sibling schedule_pause in the period parameter description, making selection unambiguous for an agent.

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?

Explicitly tells when to use this tool: 'This is the answer to pause this client for October' and contrasts with schedule_pause, which stops the whole schedule and back-bills missed periods. This gives clear when-to-use and when-not-to-use guidance.

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