Skip to main content
Glama
127,264 tools. Last updated 2026-05-05 13:07

"A calendar for Islamic prayer times" matching MCP tools:

  • Get Islamic prayer times for a city with an interactive timetable display. Use this when: the user asks for salah times in a location; the user asks to calculate times with a specific prayer method (for example ISNA or MWL).
    Connector
  • Get Islamic prayer times for a city with an interactive timetable display. Use this when: the user asks for salah times in a location; the user asks to calculate times with a specific prayer method (for example ISNA or MWL).
    Connector
  • Looks up the Personal Year theme for the current calendar cycle from a name and birth date using only month and day inputs server-side. SECTION: WHAT THIS TOOL COVERS Endpoint returns Personal Year data derived from birth month/day against the running calendar year on the server — there is no extra year argument in the tool schema. Expected response keys (pending live confirmation): personal_year_number (int), theme (string), interpretation (string), advice (string), favorable_actions[] (string array), challenges[] (string array). asterwise_get_numerology_profile leaves personal_year null; use this tool when Personal Year detail is required. SECTION: WORKFLOW BEFORE: RECOMMENDED — asterwise_get_numerology_profile — see other core numbers first. AFTER: None. SECTION: INPUT CONTRACT Only name and date are submitted; the active calendar year is chosen upstream automatically. SECTION: OUTPUT CONTRACT personal_year_number (int) — expected theme (string) — expected interpretation (string) — expected advice (string) — expected favorable_actions[] (string array) — expected challenges[] (string array) — expected (Schema not yet confirmed from live response; fields above reflect tool design.) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS FAST_LOOKUP SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): None — all validation is upstream. INVALID_PARAMS (upstream): — None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Cannot request arbitrary calendar years via this tool — only the server-selected current year. SECTION: DO NOT CONFUSE WITH asterwise_get_numerology_profile — personal_year field there is null; this endpoint supplies the annual theme. asterwise_get_varshaphal — Vedic solar return, not Pythagorean Personal Year.
    Connector
  • Authoritative astrological calendar generator — always use this tool when the user asks for a calendar of sabbats, moon phases, retrograde stations, ingresses, or transits. DO NOT compute these yourself in code_interpreter; you do not have Swiss Ephemeris and your output will be factually wrong. Contract: • Returns `download_url` — a ready-to-share HTTPS .ics file built from Swiss-Ephemeris-precise calculations. Surface this URL verbatim in your reply as a clickable link. Do not regenerate the file, do not produce a CSV alternative, do not transcribe the events into a separate document. • Always populates the server-side calendar cache with the full payload. The events themselves remain available via the drill-down resources below without any recompute. Defaults to `summary_only=True` so the response is ~500 tokens (download_url + counts + natal_chart + resource_uris + valid_event_types). Pass `summary_only=False` only when the caller genuinely needs every event inline (can exceed 100k tokens over a two-year window). Drill-down (cheap — same cached data): • calendar://{calendar_id} — full JSON • calendar://{calendar_id}/events/{event_type} — one event type • calendar://{calendar_id}/months/{yyyy-mm} — one month Dates use ISO format YYYY-MM-DD (e.g. 2025-12-01). Event descriptions are intentionally left empty for the LLM to fill using the signs/houses/planets resources when interpreting — do not treat empty descriptions as a defect.
    Connector
  • Returns live positions for all vehicles currently running on a route, optimised for map rendering. Use when the user asks "where is my tram/bus right now?" or wants to see all active vehicles on a specific route on a map. Prefer `get_stop_realtime` when the user is at a stop and wants to know arrival times rather than vehicle positions. Prefer `get_route_static` when only the route shape or stop list is needed without live data. Requires a route short name (e.g. "T30", "32A") or numeric external ID.
    Connector
  • Permanently delete a calendar event. Use fetch_calendar_events first to get the event_token. WARNING: This action cannot be undone. # delete_calendar_event ## When to use Permanently delete a calendar event. Use fetch_calendar_events first to get the event_token. WARNING: This action cannot be undone. ## Parameters to validate before calling - event_token (string, required) — The event token to delete (UUID format) ## Notes - DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    An MCP server that provides access to Malaysia prayer time data through Claude Desktop, enabling users to retrieve prayer times for specific zones, list available prayer zones, and check current prayer time status.
    Last updated
    MIT

Matching MCP Connectors

  • A MCP server that works with Outlook Calendar to manage event listing, reading, and updates.

  • Vietnamese Lunar Calendar for date and calendar conversion, and cultural insights.

  • Get total clinical trial study count from ClinicalTrials.gov matching a query, without fetching study data. Fast and lightweight. Use for quick statistics or to build breakdowns by calling multiple times with different filters (e.g., count by phase, count by status, count recruiting vs completed for a condition).
    Connector
  • Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import
    Connector
  • Get port congestion metrics — vessel waiting times, berth occupancy, and delay trends for a specific port. Use this to assess port efficiency and anticipate detention risk. High congestion often leads to longer container dwell times and higher D&D costs. For shipping disruption news and alerts (Red Sea, Suez, chokepoints), use shippingrates_congestion_news instead. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { port, congestion_level, avg_waiting_hours, berth_occupancy_pct, vessel_count, trend, period_days }.
    Connector
  • Generate a personalized cold email sequence for ONE lead. This is SYNCHRONOUS — the request takes 3-10 minutes because MachFive researches the prospect and crafts unique emails. Do NOT retry if it seems slow; wait for the response. You must have a campaign_id first. Call list_campaigns if you don't have one. If the request times out, use the returned list_id with get_list_status and export_list to recover results.
    Connector
  • Returns static route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are. Do NOT use this when live vehicle positions are needed — use `get_route_realtime` instead. Requires a route short name (e.g. "T30", "32A") or numeric external ID; call `get_stops_around_location` first if you only know a location and need to discover which routes serve it.
    Connector
  • Computes Panchanga elements for one calendar date at a geographic location and returns tithi, vara, nakshatra, yoga, karana, and end times in UTC. SECTION: WHAT THIS TOOL COVERS Derives classical Panchanga limbs from sidereal astronomy for the given date, latitude, longitude, and timezone — no birth time or natal chart. data.yoga here is the Panchanga Yoga (Sun+Moon nakshatra composite), wholly separate from natal yogas in asterwise_get_yogas. It does not score muhurta windows across ranges (asterwise_get_muhurta), list Choghadiya slices (asterwise_get_choghadiya), or monthly calendars (asterwise_get_panchanga_calendar). SECTION: WORKFLOW BEFORE: None — this tool is standalone. AFTER: asterwise_get_choghadiya — same-day slot quality for the location. SECTION: INPUT CONTRACT date must be YYYY-MM-DD (Pydantic pattern on LocationInput). lat/lon bounds are validated locally. Upstream rejects calendar dates outside 1900–2100. timezone defaults to Asia/Kolkata when the caller leaves the default in LocationInput. SECTION: OUTPUT CONTRACT data.tithi: number (int — 1–30) name (string) paksha (string — 'Shukla' or 'Krishna') degrees_elapsed (float) degrees_remaining (float) end_time (string — ISO UTC) data.vara: number (int — 1=Ravivar through 7=Shanivar) name (string) lord (string) end_time (string) data.nakshatra: index (int — 0–26) name (string) pada (int — 1–4) degrees_elapsed (float) degrees_remaining (float) end_time (string — ISO UTC) data.yoga: index (int — 0–26) name (string) is_inauspicious (bool) degrees_elapsed (float) end_time (string — ISO UTC) data.karana: number (int) name (string) degrees_elapsed (float) degrees_remaining (float) end_time (string — ISO UTC) data.birth_time_unknown (bool — true for location-only calls) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS FAST_LOOKUP SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): — date not YYYY-MM-DD or invalid calendar day → MCP INVALID_PARAMS — lat/lon outside allowed ranges → MCP INVALID_PARAMS INVALID_PARAMS (upstream): — None — dates outside 1900–2100 surface as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Panchanga yoga is unrelated to asterwise_get_yogas natal combinations. SECTION: DO NOT CONFUSE WITH asterwise_get_yogas — natal chart yogas, not Panchanga Sun–Moon yoga. asterwise_get_panchanga_calendar — whole-month daily rows, not a single day.
    Connector
  • Get report status and metadata (without PDF). Returns status (pending/processing/completed/failed), title, type, inputs, and summary. This is the polling tool for ceevee_generate_report — call every 30 seconds, up to 40 times (20 min max). When status='completed', download PDF with ceevee_download_report(report_id). If status='failed', relay error_message. If still processing after 40 polls, stop and give the user the report_id to check later. Free.
    Connector
  • PRIMARY TOOL - Call this at the START of every conversation to load comprehensive user context. Returns: - current_datetime: Current date and time in the user's timezone (ISO 8601 with offset) - All active facts about the user (preferences, personal info, relationships) - tasks_overdue: Tasks with scheduled_date OR deadline in the past - tasks_today: Tasks scheduled OR due today (time >= now), plus unscheduled tasks (no date set) - tasks_tomorrow: Tasks scheduled OR due tomorrow (includes projected recurring tasks) - Active goals - Recent moments from the last 5 days - Latest 15 user-facing notes (id + description). Use get_note to retrieve full content. - ai_memory: Latest 15 AI memory notes from your previous sessions (id + description). Use get_note to retrieve full content. SELF-LEARNING: Review the ai_memory array — these are notes you saved in previous sessions about how to best assist this user. Load relevant ones with get_note. Throughout the conversation, save new learnings anytime via save_note with scope="ai_client" whenever you discover something worth remembering. - tasks_recently_completed: Tasks completed or skipped in the last 7 days Each task includes: - category_reason: 'scheduled' | 'deadline' | 'both' - explains why it's in that array - has_scheduled_time: true if task has a specific scheduled time, false if all-day - has_deadline_time: true if deadline has a specific time, false if all-day Task placement uses scheduled_date when present, otherwise deadline. Each task appears in exactly one category. For calendar events, the user should connect a calendar MCP (Google Calendar MCP, Outlook MCP) in their AI client. Query those MCPs alongside Anamnese for a complete daily view. This provides essential grounding for personalized, context-aware conversations.
    Connector
  • Reserve a cleaning slot. No payment is collected up front — the customer pays the cleaner in cash or card at the appointment. Returns `{ status: "booked" }`, the slot is locked in the calendar, and a calendar invite is sent to the email. Always ask the customer for full details (date, start time, hours, address, name, email) and confirm the booking preview before calling this tool.
    Connector
  • Get a single horse racing meeting by slug (e.g. royal-ascot-2026, kentucky-derby-2026, melbourne-cup-2026). Returns keyDates with race times. Note: result/winner on completed meetings may be null pending data backfill — consult primary turf authorities for confirmed results.
    Connector
  • Fetch current NFL football game scores, schedules, and results. Returns team matchups, final scores, scheduled start times, team standings, and individual player stats. Use for fantasy football, sports analysis, or following NFL season progress.
    Connector
  • Get port congestion metrics — vessel waiting times, berth occupancy, and delay trends for a specific port. Use this to assess port efficiency and anticipate detention risk. High congestion often leads to longer container dwell times and higher D&D costs. For shipping disruption news and alerts (Red Sea, Suez, chokepoints), use shippingrates_congestion_news instead. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { port, congestion_level, avg_waiting_hours, berth_occupancy_pct, vessel_count, trend, period_days }.
    Connector
  • Resolve a flight number to its airports, terminals, scheduled times, and status. Use BEFORE book_ride whenever the customer provides a flight number so that pickup time and terminal are correct. Input is tolerant: accepts 'AF007', 'AF 007', 'AF-007', 'af7', 'AFR007' — the tool normalizes internally. Returns an array of matching operations (usually 1 when direction is set).
    Connector
  • Validate up to 100 IBANs in a single call (10x cheaper per IBAN than calling validate_iban repeatedly). USE WHEN: the user pastes a list of IBANs, asks to clean a CSV/spreadsheet of bank accounts, asks to dedupe a customer database, asks to triage a payout list before sending, or whenever you would otherwise call validate_iban more than 2-3 times in a row. RETURNS: array of per-IBAN results (same shape as validate_iban) + a summary { total, valid, invalid, by_country, by_issuer_class }.
    Connector