Skip to main content
Glama

update_scheduling_settings

Idempotent

Set a workspace's scheduling timezone and/or posting cadence (same fields Settings > Scheduling in the web app edits). Omit a field to leave it alone.

timezone must be a valid IANA name (e.g. "Asia/Kolkata", "America/New_York") — ask the user for this rather than guessing from their apparent location. posting_days uses JS-style weekday numbers, 0=Sunday...6=Saturday; omit or pass [] for "every day". posting_slots are 24h "HH:MM" wall-clock times in that timezone, e.g. ["09:00", "18:00"]; omit or pass [] to fall back to a single 18:00 slot.

Call this once per workspace when timezone is unset (get_posting_slots and list_workspaces both surface timezone="" for that case) — after this, future get_posting_slots calls use the saved settings without asking again.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "update_scheduling_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNo
posting_daysNo
workspace_idYes
posting_slotsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false); the description goes further by disclosing partial-update semantics ('Omit a field to leave it alone'), the non-obvious null defaults (omit/[] → every day; omit/[] → single 18:00 slot), and persistence into later reads. These fallbacks cannot be inferred from the schema, where every field simply defaults to null.

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?

Four short paragraphs, each doing distinct work: purpose/omit semantics, timezone rule, posting_days and posting_slots formats, then the when-to-call trigger. No filler and the core intent is front-loaded in the first sentence.

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

Completeness5/5

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

For a 4-parameter mutation tool with rich annotations and an existing output schema, this covers everything an agent needs: when to invoke, how to source the timezone value, format of each field, what omission means, and the effect on subsequent reads. No return-value description is needed given the output schema.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: IANA name format with examples, JS weekday numbering 0=Sunday..6=Saturday, 24h 'HH:MM' wall-clock times interpreted in the saved timezone, plus the empty-array semantics for both list parameters. Only workspace_id is left implicit, which is self-evident.

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?

Opens with a specific verb+resource+scope: 'Set a workspace's scheduling timezone and/or posting cadence', and anchors it to the equivalent UI surface (Settings > Scheduling). An agent can tell immediately which fields this mutates and that it is not a scheduler-runner or automation tool.

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?

Gives an explicit trigger condition: 'Call this once per workspace when timezone is unset (get_posting_slots and list_workspaces both surface timezone="" for that case)'. It also names the downstream consequence that future get_posting_slots calls won't re-prompt, and warns to ask the user rather than guess the timezone.

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