Skip to main content
Glama

Iqamah prayer times

Mosques near a place

find_mosques_near
Read-only

Mosques near a point, nearest first, with their ids for get_mosque_times. has_source says whether we can read the mosque's own times.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_mosques_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly mosques whose name contains this (case and accents ignored).
limitNo
latitudeYes
longitudeYes
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety behavior is covered. The description goes beyond that by disclosing the default result ordering ('nearest first') and the meaning of a returned field ('has_source says whether we can read the mosque's own times'), which is real behavioral context an agent cannot get from annotations. It omits defaults/limits on result count and empty-result behavior.

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, front-loaded with the core behavior and then the follow-on field semantics. Every clause carries information; there is no boilerplate or repetition of the schema.

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?

There is no output schema, and the description partially covers that gap by naming the returned ids, ordering, and has_source. However, with five parameters at 20% schema coverage, the search-tuning parameters (radius_km, limit, name) are left unexplained, so the definition is only minimally sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% — only the 'name' parameter is documented in the schema, while limit, latitude, longitude and radius_km carry only type/bounds/enum metadata. The description adds nothing about any parameter: it does not explain the radius_km options or default of 10, the limit cap of 50, or how the name filter interacts with ranking. With a low coverage schema, the description needed to compensate and does not.

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 and scope ('Mosques near a point') and adds the result ordering ('nearest first'), which makes the tool's output shape immediately clear. It also ties itself to the sibling by saying the returned ids are meant for get_mosque_times, so an agent can place it in the workflow. It stops short of a 5 because there is no explicit verb and the differentiation from get_prayer_times is left implicit.

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 rather than stated: the mention of 'ids for get_mosque_times' tells the agent this is a discovery step that precedes a times lookup. There is no explicit when-to-use/when-not guidance, no statement about what to do when no mosques are found, and no comparison against get_prayer_times.

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