Skip to main content
Glama
Sign In

Suara

by com.trysuara
OverviewDiscussionsAdmin

Festive posting calendar

festive_calendar
Read-onlyIdempotent

Use this when someone wants to plan posts around festivals and holidays in Malaysia, Canada or Brunei: when to start posting for each one, who it matters most to and what to post, for example 'when should my bakery start posting for Chinese New Year?'. Returns the dates from Suara's free posting calendars on trysuara.com (the same files people add to Google, Apple or Outlook), marking dates that can still change. For official public holiday lists in other countries use holiday_calendar. Do not invent dates it doesn't return.

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": {
      "country": "<country>"
    },
    "name": "festive_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD, optional (default a year from the start)
fromNoStart date YYYY-MM-DD, optional (default today)
countryYesWhich calendar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish it as a safe, idempotent, closed-world read, so the description's added value is provenance and reliability: dates come from Suara's free posting calendars on trysuara.com and some are marked as still subject to change. It also warns against fabricating dates outside the response, which is real behavioral guidance. It stops short of describing granularity (festival count, whether recurring dates are included), so not a 5.

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 trigger condition, followed by the output description, the alternative tool, and a guardrail. Every clause earns its place, though the single long sentence with embedded example is dense and could be split for scanability.

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 no output schema, the description carries the burden of explaining returns, and it does: festival dates plus timing, audience and content guidance, with uncertain dates flagged. Minor gaps remain on result shape and whether non-festival dates are filtered, but an agent has enough to call it correctly.

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% and already documents the country enum and the default behaviour of from and to. The description restates the country scope but adds no format, range-limit or timing semantics 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: planning social posts around festivals and holidays in Malaysia, Canada or Brunei, with what each festival means for posting timing, audience and content. The concrete example query ('when should my bakery start posting for Chinese New Year?') makes the intended use unmistakable and separates it from holiday_calendar.

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?

Explicitly gives the triggering intent ('when someone wants to plan posts around festivals'), names the alternative for a different need ('for official public holiday lists in other countries use holiday_calendar'), and adds a negative constraint ('Do not invent dates it doesn't return').

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

All Suara 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