Skip to main content
Glama

Wadifa Info: Morocco Public Jobs

Morocco public holidays

public_holidays
Read-only

Moroccan public holidays for this year and next. Islamic holidays carry approximate=true until the Ministry of Habous confirms the moon sighting.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description adds real value beyond them by disclosing a data-quality caveat: Islamic holidays are flagged approximate=true until Ministry of Habous confirmation. That caveat is exactly the kind of behavioral context an agent needs before presenting dates as final.

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

Conciseness5/5

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

Two short sentences, zero repetition of the title, and the most important constraint (coverage window) is front-loaded. Every sentence earns its place, including the accuracy caveat.

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?

For a zero-parameter read-only lookup with no output schema, the description covers scope and the key reliability caveat. It leaves the return shape undocumented, though that is a minor gap given the simplicity and the annotations' safety profile.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline applies. The description does not need to explain inputs, and it uses its space for the temporal scope instead.

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 a specific resource (Moroccan public holidays) and a bounded scope (this year and next), which lets an agent distinguish it from the sibling school_holidays. It stops short of explicitly naming that sibling or stating that school holidays are excluded, so it is clear but not fully differentiated.

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 only implied: an agent can infer this is the tool for national holidays, but the description never says when to prefer it over school_holidays or how to handle a request outside the current/next-year window. No exclusions or prerequisites are given.

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