Skip to main content
Glama
Sign In

SalahTable

by com.salahtable
OverviewDiscussionsAdmin

Prayer times today and this week

get_prayer_times
Read-onlyIdempotent

Fajr, sunrise, Dhuhr, Asr, Maghrib and Isha for today and the next 7 days in the city's local time, the next prayer, and Asr for the other school.

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": {
      "country": "<country>",
      "city": "<city>"
    },
    "name": "get_prayer_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug from find_city, e.g. "karachi", "london"
methodNoCalculation method; defaults to the country's usual method
schoolNoAsr school; defaults to the country's usual school
countryYesCountry slug from find_city, e.g. "pakistan", "united-kingdom"

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, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely non-annotated behavior by disclosing the return contents (six prayer events, the next prayer, and the alternate-school Asr), which is meaningful given there is no output schema.

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 dense sentence that front-loads the returned values and then adds the two supplementary outputs; every clause carries information. It reads as a compressed list rather than a structured statement, which limits it slightly.

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 does the important work of describing the response payload, including time zone framing and extra fields. Remaining gaps (method/school defaults, slug sourcing) are already handled by the schema descriptions, so little is missing for correct invocation.

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 100% with descriptions and enums for method and school, so the schema carries the parameter burden and the baseline applies. The phrase 'the other school' hints that both schools' Asr is returned regardless of the school argument, which is a small but useful clarification beyond the schema.

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 exact resource (Fajr, sunrise, Dhuhr, Asr, Maghrib, Isha times) and the time window (today plus next 7 days), which distinguishes it from the monthly timetable sibling without naming it. It is a clear content listing rather than a clear verb+resource phrasing, keeping it just below the top score.

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?

The 8-day window implicitly tells an agent when this tool fits versus get_monthly_timetable, and the local-time framing implies it is the per-city daily view. However, the description never states an explicit condition for choosing it over the monthly sibling, nor prerequisites like resolving slugs via find_city.

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

All SalahTable toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources