Mark

Set Workspace Timezone

set_workspace_timezone

Idempotent

Sets the workspace IANA timezone. Only org admins can call it. Each channel keeps its posting time as a local clock time, so real posting instants move. Already-scheduled posts keep their times. Related: get_workspace, get_calendar, update_posting_slots.

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": {
      "timezone": "<timezone>"
    },
    "name": "set_workspace_timezone"
  }
}

Input Schema

Name	Required	Description	Default
`timezone`	Yes	IANA time zone, such as America/New_York. Not EST or +05:00.

Output Schema

Name	Required	Description	Default
`newTimezone`	Yes
`oldTimezone`	Yes
`affectedSlotCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the semantic side effect: channels keep posting as local clock times so real posting instants shift, while already-scheduled posts retain their times. That is exactly the consequence an agent needs to warn a user about before mutating a workspace setting.

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 sentences plus a related-tools line, front-loaded with the action and the admin gate, then the behavioral consequence. Nothing redundant and nothing buried.

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?

A single-parameter mutation tool with full annotations and an output schema; the description covers the permission gate and the non-obvious scheduling effects, which is everything an agent needs before calling it.

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 coverage is 100% and the schema itself already gives the IANA format plus explicit counterexamples (not EST, not +05:00). The description only restates 'IANA timezone', adding no meaning beyond the schema, so baseline 3 applies.

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 ('Sets the workspace IANA timezone') with the exact scope of the setting. No sibling tool in the list touches workspace-level timezone, so it is unambiguous.

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?

Gives a hard prerequisite ('Only org admins can call it') and names the related tools an agent should read first (get_workspace, get_calendar, update_posting_slots). It stops short of explicitly saying when to prefer those reads or what to do instead, but the call context is clear.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?