Skip to main content
Glama
Sign In

Postfjord

by com.postfjord
OverviewDiscussionsAdmin

List calendar

postfjord_list_calendar
Read-only

Posts scheduled between two dates (ISO 8601), or by status (draft, scheduled, publishing, published, partial, failed, cancelled). With both from and to, the answer also has notes: the calendar notes on those days (a sale, a holiday, a course start), as postfjord_list_calendar_notes gives them.

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": "postfjord_list_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD for a whole day in the workspace time zone, or an ISO date-time. Inclusive
fromNoYYYY-MM-DD for a whole day in the workspace time zone, or an ISO date-time. Inclusive
limitNoHow many posts at most.
statusNoOnly posts in this state, instead of a date range.

Output Schema

NameRequiredDescriptionDefault
itemsNoThe posts.
notesNoCalendar notes on the days asked for, when from and to are both days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many posts at most."
    • addedInput schema / properties / status / description
      Added value: +"Only posts in this state, instead of a date range."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "draft",
+  "scheduled",
+  "publishing",
+  "published",
+  "partial",
+  "failed",
+  "cancelled"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "items": {
+      "description": "The posts.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "baseText": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {
+              "id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Calendar notes on the days asked for, when from and to are both days."
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating. The description adds one genuinely non-obvious behavior: notes are attached to the response only when both from and to are present. It does not cover pagination, default limits, or how limit interacts with a status filter.

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 tight sentence front-loads the two selection modes before the notes caveat. The trailing clause 'as postfjord_list_calendar_notes gives them' is slightly awkward but earns its place by preventing a redundant call.

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

Completeness4/5

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

With an output schema, full annotation coverage, and 100% parameter documentation, the definition only needs to add the non-structured facts, and it does. Minor gaps remain around behavior when no parameters are passed and around limit semantics with a status filter.

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 description coverage is 100%, so dates, inclusiveness, and the status enum are already fully documented. The description contributes only the combined from+to effect, which is closer to output behavior than parameter meaning; baseline 3 is appropriate.

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?

States the resource ('Posts') and the two selection modes (date range of ISO 8601 dates, or a status value) with the enumerated states spelled out. It is clearly distinct from postfjord_list_calendar_notes, which it names explicitly, though the verb 'list' only appears in the name/title rather than the description.

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 clear selection logic: use a from/to range for scheduled posts, or a status filter for a state-based listing. It also tells the agent that the notes sibling need not be called separately when a full range is used, which is real routing guidance, but there is no explicit statement of what to do when neither parameter is supplied.

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

All Postfjord toolsInspect
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