Skip to main content
Glama

Holidays and posting guidance

get_holidays
Read-onlyIdempotent

Holidays of every major tradition (Jewish/Israeli, Muslim, Christian, Orthodox, Druze, Bahá'í, Hindu, Buddhist, Sikh, Jain, Chinese, Persian, international and commercial days) with advice per day: avoid (no promotional posts to that audience), sensitive (respectful only), opportunity (greeting or themed post), normal. It helps when picking a date for an audience, since a promotional post on a day of mourning or fasting reads badly: the traditions to look at are the ones of each account's audience.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (default: from + 60 days, max 400 days)
fromNoFirst day, YYYY-MM-DD (default: today)
languageNoen
traditionsNoLimit to some traditions: jewish, muslim, christian, orthodox, druze, bahai, hindu, buddhist, sikh, jain, chinese, persian, international (array, or comma separated in a query string)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds genuinely useful semantics by defining the four advice categories and their operational meaning for posting. It does not mention that the range is capped (max 400 days) or how results are ordered, but the added vocabulary is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The topic is front-loaded and the second sentence earns its place by explaining the avoid/sensitive grading logic. However, the parenthetical enumeration of fourteen traditions plus thirteen more in the closing clause restates the schema enum almost verbatim and bloats an otherwise two-sentence description.

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 usefully characterizes what each returned day carries, which is the main thing an agent needs. Remaining gaps — the 60-day default window, the 400-day ceiling, and what `language` changes — are documented in the schema for the dates but nowhere for language, a minor omission for a 4-parameter read-only lookup.

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 75%, so the baseline is 3. The description's only parameter-adjacent content is re-listing the tradition names, which duplicates the enum in the schema rather than adding meaning, and it says nothing about the unexplained `language` parameter or about combining traditions with the date window.

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?

The description clearly states the resource (holidays across a long list of traditions) and adds the distinctive payload of per-day posting advice (avoid/sensitive/opportunity/normal), which an agent could not infer from the name. It does not name or contrast with the closest sibling, get_best_times, which also answers 'when should I post', so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is given only as an implied scenario: 'It helps when picking a date for an audience', plus a rationale about why a promotional post on a mourning day reads badly. There is no explicit when-not guidance and no named alternative (e.g., get_best_times for engagement optimization versus this tool for cultural risk), so the agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources