Postemi: Social Media Scheduler

get_workspace_context

Read-only

Get the current time and the user's timezone before you compute any post date.

Call this FIRST in any conversation that mentions a time — "tomorrow at 9", "next Tuesday", "in two hours". Postemi stores post dates in UTC, and create_post refuses a scheduled date in the past, so a wrong timezone assumption is a failed call at best.

Returns the server's current UTC instant, the user's IANA timezone as they set it in Postemi, and the matching local time. If "timezone" comes back null the user has never set one — ask them for it rather than assuming, and say the timezone back to them whenever you quote a time.

Also returns the workspace this connection acts on. A user can have several workspaces; list_workspaces shows them all and switch_workspace moves the connection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workspace_context"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`output`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say readOnly/non-destructive; the description adds the failure mode that matters — create_post refuses past dates and post dates are stored in UTC, so a wrong timezone assumption causes a failed call. It also discloses the null-timezone edge case and the instruction to ask the user rather than assume.

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?

Front-loaded with the action and the 'call this first' rule, and each paragraph has a distinct job (why, what, workspace). Slightly long for a zero-param getter — the timezone-null guidance and workspace paragraph could be tightened without losing meaning.

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?

Given zero params, a read-only annotation set and an existing output schema, the description covers everything left: when to call, why it matters, what the edge case (null timezone) means, and the sibling tools to reach for workspace management. No ambiguity remains for correct invocation.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description instead spends its words on return-value semantics (UTC instant, IANA timezone, local time, workspace), which is above baseline but partially redundant with the existing output 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?

States a specific verb and resource (get the workspace context: current time, timezone, workspace) and immediately distinguishes itself from list_workspaces and switch_workspace by naming them. An agent can tell what it returns without opening the schema.

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?

Explicit call-ordering instruction ('Call this FIRST in any conversation that mentions a time'), concrete trigger examples ('tomorrow at 9', 'next Tuesday'), and named alternatives (list_workspaces, switch_workspace) for the multi-workspace case. Nothing is left to inference.

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

All Postemi: Social Media Scheduler 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.