Skip to main content
Glama

Iqamah prayer times

A mosque's iqamah times

get_mosque_times
Read-only

One mosque's congregation (iqamah) and Jumu'ah times as the mosque publishes them, from today on, with the azaan times. status says whether they are fresh, stale (latest we have), queued (not read yet) or none.

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": {
      "mosque_id": "<mosque_id>"
    },
    "name": "get_mosque_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
mosque_idYesThe id from find_mosques_near.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 isn't needed for safety. It adds real behavioral context instead: the data is published by the mosque, starts from today, and carries a status field enumerating fresh/stale (latest available)/queued (not yet read)/none — telling the agent how to interpret missing or lagging data.

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?

Two sentences, front-loaded with what is returned, followed by the status semantics. Dense but every clause carries information; only the parenthetical glosses add slight bulk without waste.

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 names the returned fields (iqamah, Jumu'ah, azaan) and explains status, which is the highest-risk output for misinterpretation. The uncovered days parameter is the main omission for a two-parameter tool.

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 50%: mosque_id is documented in the schema, while days (1–7, default 1) is undocumented everywhere. The phrase 'from today on' hints that results project forward, but the description never explains that days controls how many days of times are returned, leaving a real gap.

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?

Specific verb and resource: returns one mosque's iqamah (congregation) and Jumu'ah times plus azaan times, explicitly scoped 'from today on'. It is clearly distinct from a general prayer-times tool and from find_mosques_near, though it never names a sibling as an alternative.

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 implied by 'One mosque's congregation (iqamah) and Jumu'ah times' plus the required mosque_id, whose schema description points back to find_mosques_near. There is no explicit when-to-use/when-not guidance versus get_prayer_times, so the agent must infer the selection rule.

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