Mark

Get Calendar

get_calendar

Read-onlyIdempotent

Shows the publishing calendar for one week: each day's scheduled and published posts in time order, the open posting slot positions to fill, and how many of each channel's slot posts are filled. A slot is a weekday and a number of posts that day; each open position has its slot id and local date (which reschedule_post takes to fill it), its time (the channel's posting time plus 3 hours per post already that day, or now once that has passed today) and filled out of count. An approved social post's card carries handoff, as in get_post: handing_off before it reads scheduled, or stuck with the reason and fix; an approved LinkedIn Article's reads publish_by_hand, or publish_now once its time has passed. Each post card carries its pillar name (pillar, null when it has none) and pillarId, so you can filter a week by pillar or channel yourself. Pass week as any date in it (YYYY-MM-DD); for a month, call it once per week. Times render in the workspace timezone, or in timezone if you pass an IANA name (render only; stored data does not change). Related: save_post, reschedule_post, update_posting_slots.

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_calendar"
  }
}

Input Schema

Name	Required	Description
`from`	No	Same as week, for older callers.
`week`	No	Any date in the week to show (YYYY-MM-DD). Defaults to today.
`timezone`	No	IANA zone to render times in. Does not change stored data. Defaults to the workspace timezone.

Output Schema

Name	Required	Description	Default
`calendar`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA zone to render times in. Does not change stored data. Defaults to the workspace timezone.",
+  "type": "string"
+}

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With readOnly/idempotent/non-destructive already in annotations, the description adds substantial beyond-schema context: how open-position times are computed (posting time + 3 hours per existing post, or now once passed), the handoff/stuck states on post cards, publish_by_hand vs publish_now semantics, and that timezone is render-only and does not mutate stored data.

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?

Purpose and scope are front-loaded in the first sentence, and the dense second/third paragraphs carry non-obvious semantics rather than filler. The slot-time computation sentence is long and could be broken up, but nearly every clause earns its place.

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?

Safety is covered by annotations and return shape by the output schema, so the description's job is interpretation—which it fully delivers via timezone behavior, slot fill semantics, and post-card state flags. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by clarifying that week accepts any date within the week and that iterative per-week calls cover a month, and by reinforcing that timezone is render-only. It omits the legacy 'from' parameter entirely, leaving that alias to the 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 concrete verb+resource ("Shows the publishing calendar for one week") and enumerates exactly what is returned: scheduled/published posts in time order, open slot positions, and per-channel fill counts. This is clearly distinct from siblings like get_post, search_posts, or get_weekly_brief.

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 explicit calling guidance for the main parameter ("Pass week as any date in it") and a scaling rule ("for a month, call it once per week"), plus a Related list naming save_post, reschedule_post, and update_posting_slots. It does not explicitly state when-not-to-use or differentiate from search_posts/get_weekly_brief, so it falls short of a 5.

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?