Skip to main content
Glama

prayer_times_calendar

Read-onlyIdempotent

Get prayer times for an entire month in one call.

Instructions

Get prayer times for an entire month in one call.

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": {
      "city": "<city>",
      "month": "<month>",
      "year": "<year>"
    },
    "name": "prayer_times_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g., "Dubai").
yearYesGregorian year.
monthYesMonth number, 1 to 12.
methodNoCalculation method ID. 8 = Gulf Region (default).
schoolNoAsr school. 0 = Shafi (default).
countryNoCountry name. Defaults to "United Arab Emirates".United Arab Emirates

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing behavioral beyond that — no note on data source, calculation-method effects on results, or whether results vary by country/method. It neither contradicts nor enriches the annotations.

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?

A single tight sentence with the resource and scope front-loaded and no filler. 'In one call' is mildly redundant with 'entire month' but costs little.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and the schema fully documents inputs. The remaining gap is the absence of any routing information versus prayer_times_for, which is the one thing an agent needs beyond structured fields.

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% with all six parameters (city, year, month, method, school, country) documented including defaults and examples. The description adds no parameter-level meaning, so the baseline 3 applies when the schema does all the work.

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 verb (Get) and resource (prayer times) with an explicit scope qualifier (entire month in one call), so an agent knows this is the bulk/monthly variant. It does not name the sibling prayer_times_for, so the differentiation from the single-day tool 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 Guidelines2/5

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

The phrase 'in one call' hints at a batching use case but there is no explicit when-to-use guidance, no exclusion conditions, and no mention of prayer_times_for as the alternative for a single day. The agent must infer the routing decision entirely.

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

Deploy Server

Other Tools