Skip to main content
Glama

Set your seller holiday

growwer_put_seller_holiday
DestructiveIdempotent

Start, change, or end a seller's holiday so their media stop taking orders during the break; updating the same holiday leaves existing settings unchanged.

Instructions

Use this when a seller wants to start, change or end their holiday: while on holiday their medias take no orders. Setting the holiday they already have changes nothing.

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": {
      "requestId": "<requestId>",
      "onHoliday": "<onHoliday>"
    },
    "name": "growwer_put_seller_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNo
onHolidayYes
requestIdYesRequired. A new UUID for each distinct write (8 to 128 letters, digits, ".", "_", ":" or "-"). Calling the tool again with the same requestId and arguments returns the first result without writing twice; send a new one for a new write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description reinforces the idempotent half ("Setting the holiday they already have changes nothing") and adds real value by explaining the effect — media take no orders while away. It does not explain what happens to in-flight orders, how the holiday is later ended, or what happens if endDate is null, which are the meaningful unknowns for a destructive write. No contradiction with the declared hints.

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?

One compact sentence with the usage trigger front-loaded and the consequence attached immediately after. Nothing is padded, though the final clause about re-setting is slightly cryptic in phrasing.

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?

Annotations carry the safety profile and there is no output schema to describe, so the description only needs to cover behaviour and parameters. It covers the behaviour consequence but leaves two of three parameters, including the undefined endDate, entirely undocumented — a real gap for a destructive mutation.

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

Parameters2/5

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

Schema coverage is only 33% — requestId is documented in the schema, but endDate and onHoliday are bare booleans/strings with no description anywhere. The description never mentions the endDate field or explains how onHoliday=false interacts with a supplied endDate, so the one genuinely ambiguous parameter pair is left entirely unexplained.

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 gives a specific verb (start/change/end) against a specific resource (the seller's holiday), plus the operational consequence that media take no orders. No sibling tool touches holiday state, so the scope is unambiguous even without naming an alternative.

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?

"Use this when a seller wants to start, change or end their holiday" is an explicit trigger covering all three lifecycle cases. It stops short of exclusions or prerequisites (e.g. whether the seller must be authenticated as a seller, whether an ongoing order is affected), but no competing tool exists to route away from.

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

Deploy Server

Other Tools