Skip to main content
Glama

Prayer times and sun times

Prayer time calculation methods

prayer_methods
Read-onlyIdempotent

The calculation methods available (fajr and isha angles), and the countries where each is the default.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the result is a mapping of methods (with angles) to default countries, which partly substitutes for the absent output schema, but says nothing about stability, list size, or whether it changes over time.

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 compact sentence with no filler, front-loading the substance. It is a sentence fragment without a leading verb ('Returns...'/'Lists...'), a minor stylistic weakness but nothing wasted.

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 reference lookup with no output schema, the description covers what will come back and implicitly why it matters. The only real gap is not tying the returned methods to the sibling prayer_times tool that would consume them.

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 no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is 100% of an empty object.

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 names the resource (calculation methods) and specifies the payload contents: fajr and isha angles plus the countries where each method is the default. That is far more specific than the title, though it never contrasts itself with prayer_times or sun_times.

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 only — the description reads as a reference catalog, so an agent can infer it should consult this before choosing a method for a prayer_times call. There is no explicit statement of when to use it or that it is the lookup for a method identifier.

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