Skip to main content
Glama
Sign In

SalahTable

by com.salahtable
OverviewDiscussionsAdmin

Monthly prayer timetable

get_monthly_timetable
Read-onlyIdempotent

Daily prayer times for a whole month, from two months back to twelve months ahead of the city's current month.

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>",
      "month": "<month>"
    },
    "name": "get_monthly_timetable"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug from find_city, e.g. "karachi", "london"
monthYesMonth as YYYY-MM, e.g. "2027-02"
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

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile is covered. The description's contribution is the valid month window, which is genuinely useful and not in the annotations, but it omits the failure mode for out-of-range months and says nothing about defaults applied when method/school are omitted.

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?

One front-loaded sentence with zero filler and the scope plus constraint in the right order. It is tightly written, though the brevity leaves the definition leaning heavily on 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?

For a 5-parameter, 3-required read tool with no output schema, the definition covers what is returned (a month of daily times) and the valid range. It leaves gaps on defaults applied to method/school when omitted, the error behavior outside the window, and the shape of the returned timetable.

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%, so city, country, month, method and school are all documented with formats and defaults in the schema itself. The description only alludes to the city's current month as a reference point and adds no parameter-level meaning beyond that.

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?

"Daily prayer times for a whole month" gives a concrete resource plus a scope qualifier (whole month) that separates it from the day-level get_prayer_times sibling. It stops short of naming the sibling, but the monthly granularity is unambiguous.

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 supported window (two months back to twelve months ahead) implicitly tells the agent when this tool is usable, but there is no explicit statement about choosing this over get_prayer_times for single-day queries or what to do for out-of-window months. Usage is inferable rather than stated.

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