Skip to main content
Glama
305,038 tools. Last updated 2026-07-22 22:10

"A travel guide for a 5-day road trip during the May Day holiday from Shenyang" matching MCP tools:

  • Call when the user asks about timing a decision for a specific date, or wants to pick the best day from a multi-day window. Covers trip dates, launch days, interview/meeting days, publish/send dates, travel, negotiation windows, relationship moments — any "when to X" question where the answer is a date ("should I X on April 23", "best day this month to Y", "下周四怎么样"). Modes: single date, compare up to 5 dates, or scan a range up to 31 days. Returns score (0-100), verdict, per-layer year/month/day breakdown (alerts + dimension signals), element breakdown, adverse alerts. For multi-month windows use `intentions_ask_month`; for hour precision use `intentions_ask_hour`.
    Connector
  • Look up the official public/national holidays for a country (ISO-2 code, e.g. US, IL, GB) and year from an authoritative public source (Hebcal for Israel, Nager.Date for everywhere else). Returns a DRAFT list of holiday dates: each is either a full day off or a half/partial working day (with a start/end working window). Use this to PROPOSE a holiday profile — never invent holiday dates from memory. The dates returned are authoritative for that exact year.
    Connector
  • Create and SAVE a national-holiday profile for the organization for a specific year, AFTER the user has explicitly reviewed and confirmed the holiday list. Each holiday is either a full day off or a half/partial working day (with a start/end working window). Holiday dates MUST come from suggest_holiday_profile or the user — never invent dates. Only call this once the user has confirmed; do not call it to preview.
    Connector
  • Get a price calendar showing the cheapest one-way flight price for each day in a date range. Returns a list of dates with prices - useful for finding the cheapest departure day when you have flexible travel dates. For round-trip price calendars (outbound x return date grid), use google_flights_calendar_round_trip instead.
    Connector
  • Returns the Personal Year, Personal Month, and Personal Day numbers for a given birth date and optional target date. All three cycle numbers are derived from the birth month, birth day, and the target calendar date. SECTION: WHAT THIS TOOL COVERS Personal cycles are the Pythagorean timing system. The Personal Year (1–9) sets the annual theme. The Personal Month refines it to a 30-day window. The Personal Day gives the daily energy flavour. A Personal Year 1 favours new beginnings; a 9 favours completion and release. Cycles nest: the same number in Year, Month, and Day simultaneously creates a peak intensity day. Formula: Personal Year = birth_month_reduced + birth_day_reduced + target_year_reduced Personal Month = Personal Year + target_month, reduced Personal Day = Personal Month + target_day, reduced Master numbers 11 and 22 are preserved where they arise. SECTION: WORKFLOW BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see personal cycles alongside core numbers. SECTION: INPUT CONTRACT date — Birth date in YYYY-MM-DD format. Example: '1985-11-12' year (optional int) — Target year. Defaults to current calendar year. Example: 2026 month (optional int 1–12) — Target month. Defaults to current month. Example: 5 day (optional int 1–31) — Target day. Personal Day is only returned when day is provided. Defaults to null (Personal Day omitted). Example: 1 SECTION: OUTPUT CONTRACT data.personal_year (int — 1–9 or master 11/22) data.personal_month (int — 1–9 or master 11/22) data.personal_day (int or null — null when day parameter is not provided) data.target_year (int — echoed) data.target_month (int — echoed) data.target_day (int or null — echoed) SECTION: RESPONSE FORMAT response_format=json — structured JSON. response_format=markdown — human-readable. Both modes return identical underlying data. SECTION: COMPUTE CLASS FAST_LOOKUP SECTION: ERROR CONTRACT INVALID_PARAMS (local): None — all validation is upstream. INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR SECTION: DO NOT CONFUSE WITH asterwise_get_personal_year — returns Personal Year only, no month or day breakdown. asterwise_get_numerology_profile — core name numbers; personal_year field is null there.
    Connector
  • Call when the user asks at month granularity or wants the best month from a multi-month window ("how is next month", "best month in 2026 to X", "下个月适合吗"). Use for trip-month selection, launch months, content-calendar planning, quarterly/annual decisions. Modes: single month, compare up to 5 months, or scan up to 12 months (returns top 5). Returns month score, element breakdown, adverse alerts. For day precision near the 4th–6th of a month use `intentions_ask_day`; for hour precision use `intentions_ask_hour`.
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    MCP server for business-day arithmetic with country-aware holiday calendars. It offers tools to check, calculate, and list business days and holidays for over 60 countries.
    Last updated
    9
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    An MCP App that renders an interactive dashboard in Claude conversations to unify calendar events, emails, and documents into a single interface. It enables users to manage their daily schedule and perform actions like meeting preparation through bidirectional communication between the UI and the model.
    Last updated
    2

Matching MCP Connectors

  • Composite shipment analysis in one call: volume (CBM), gross and chargeable weight, road LDM with pallet spaces and a vehicle suggestion (road mode), volumetric weight (air), revenue tonnes with a container suggestion (sea), dangerous-goods presence for items carrying un_number, and UK duty estimates for items carrying hs_code + customs_value. Provide mode (road | air | sea | multimodal) and items[] (dims in cm, weight in kg, quantity; optional stackable, pallet_type, hs_code, un_number, customs_value); origin/destination and incoterm refine the duty leg. Behavior: chains the same deterministic engines as the single-purpose tools; sections that cannot run (e.g. duty without a customs value) surface in warnings instead of failing the whole call. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: mode, itemCount, totals {pieces, grossWeight, volumeCBM, chargeableWeight, billingBasis}, modeSpecific (LDM / pallet spaces / suggested vehicle, or revenue tonnes / container), warnings and dataVersion under result — note this composite's result uses camelCase field names (legacy shape); plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: a planning summary, not a quotation or compliance determination. Related: consignment_calculator (canonical snake_case lines[] shape with advisory flags), cbm_calculator, chargeable_weight_calculator, ldm_calculator, adr_lookup, uk_duty_calculator (the engines this chains).
    Connector
  • Get the aggregate wash-report dataset: 30-day total active buyers, real-volume %, suspected_wash and self_test counts, full 8-label distribution, 14-day wash percentage time series, and five anonymized case studies (Service A through E) with pattern signals. For per-address real-time wash analysis with full signal breakdown, use the paid POST /api/v1/wash/check HTTP endpoint ($0.05 USDC) — that endpoint speaks x402, agents pay and receive data in a single HTTP round-trip. Free tier. No payment required. Returns wash-filtered data using the same v2.0 algorithm as the paid endpoints.
    Connector
  • Get bank/public holidays for a country with payment impact analysis. Returns all public holidays plus a 'payment_impact' section that shows: - Whether today is a business day or holiday in this country - Upcoming holidays in the next 14 days - Recent holidays in the last 14 days — for diagnosing a payment that is ALREADY stuck ("in progress for N days", "sent X days ago"). A recent holiday only counts if it falls INSIDE the payment's own window (on or after the send date); one that predates the send date is irrelevant and must NOT be subtracted. An empty list affirmatively means no recent holiday explains the delay — do not invent one from training data. - elapsed_business_days_by_send_date — the AUTHORITATIVE elapsed business-day count keyed by send date (weekends + this country's holidays already excluded). Use it verbatim instead of hand-counting. - Next business day and how many consecutive non-business days remain This context helps determine if holidays are causing payment delays. Args: country_code: ISO 3166-1 alpha-2 code (e.g., "US", "DE", "GB") year: Year (default: current year). Range: 2020-2030. Examples: bank_holidays("US") bank_holidays("DE", 2026) bank_holidays("GB", 2025)
    Connector
  • Searches live rental-car offers for a pickup location and rental period, optionally with a different dropoff location, pickup/dropoff times, driver age, currency, and language. Use this when the user wants to compare available rental cars, prices, vendors, categories, or booking links for a specific trip. Do not use it for flights, hotels, public transport, or general travel planning unless the user has car-rental intent. The tool queries external provider APIs in real time, returns price-ranked results grouped by SIPP/category, and may include affiliate booking links. It does not book cars, modify reservations, charge users, or store user data.
    Connector
  • Get the user's saved travel context to personalize recommendations. Returns the user's loyalty programs and elite tiers, home airport, preferred airlines and cabin, preferred hotel chains, typical trip patterns (business vs leisure, budgets, frequent destinations), and any preferences they've stated or that have been learned from past conversations. Call this once at the start of a travel or planning session and weigh it across hotel, flight, and car recommendations — it is the single best source of who this traveler is. Requires a Gondola account (API key). Returns: Formatted travel context, or instructions to build one.
    Connector
  • Active California wildfires, flagged when close to a major highway. Data: the interagency WFIGS current-wildfire feed (NIFC) - name, size in acres, percent contained, discovery date. Points are each fire's ORIGIN, not its perimeter: a large fire can affect roads far from this point. Refresh: 5-minute cache; size/containment typically update once or twice a day. Small, fast-moving local fires may appear in CHP incident logs (get_incidents, type "FIRE-Report of Fire") before this feed has them. Filters: - near_route (e.g. "I-5", "101") - only fires within ~10 miles of that highway's corridor line. - center "lat,lon" with radius_km - fires around a place, regardless of highway. Without either, every active CA fire is returned, each carrying a `near_highways` list of major corridors within ~10 miles (empty = not near a covered major highway; it may still affect local roads). This tool does NOT know about road closures caused by fires - cross-check get_incidents and get_lane_closures for the affected area.
    Connector
  • REAL action: moves the user's appointment to another free slot the SAME day, ATOMICALLY — if the target slot was just taken, the user KEEPS their current slot (never loses the held slot; that atomic guarantee is the whole point of same-day move). For a DIFFERENT day, just call book instead (a fresh booking; cross-day needs no atomic hold). No confirmation — act on request. Consent is a one-time Telegram OAuth (scope booking:write), already done — never re-prompt per action. date (YYYY-MM-DD), from (HH:MM current), to (HH:MM new).
    Connector
  • Mint the NEXT content angle(s) from the company's corpus into content_ideas + Command Center cards. Default count is 1 — do NOT bulk-fill the queue. For day-to-day drafting, prefer list_knowledge / read_knowledge (or list_corpus_inventory) to pull one chapter/passage JIT — that avoids re-tokenizing the whole book. Use promote only when a human-facing card is needed (weekly queue, Held post, operator asked). Faith grain: angles only. Never invent from empty corpus. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]
    Connector
  • Public / statutory holidays for a country (and optional state/province/region) in a given year — computed in-house, NOT scraped, so it's exact and offline-stable. Per holiday: date, name, weekday, whether it's an observed-day shift, the country, and the subdivision (when one was requested), plus the next upcoming holiday. `country` = ISO-3166 alpha-2 code (default "AU"); common names accepted ("australia", "usa", "uk", "new zealand"). 100+ countries. `year` = 4-digit year (default = current year). `subdiv` = optional subdivision code for region-specific holidays — e.g. "NSW"/"VIC"/"QLD" for AU, "CA"/"NY" for US, "ENG"/"SCT" for GB; national-level only if omitted (state lists are richer). Pairs with `market_hours`. Holiday DATES are non-copyrightable facts; computed via the open-source `holidays` library (vacanza, MIT) — commercial use + redistribution permitted, keyless. Informational only — confirm against the official gazette for legal/payroll use. Every value is returned in an Ed25519-signed, provenance-stamped envelope (source and observation time) you can verify offline against /.well-known/keys, no account required.
    Connector
  • POST /trips — Create a trip Create a new trip. Provide exactly one of `placeID` or `eventID` — the server resolves the location (city, country, country code) automatically. Use `GET /places/search` to find a placeID by city/country name first, or pass an `eventID` from `/events` to create a trip to that event's city. **Trip points** (optional `points` array, up to 20 per trip): each item is `{ note: string (max 280 chars), noteHTML?: string, placeID?: string }`. The optional `placeID` is resolved against Google Places at write time and the full Place object (city, country, lat/lon, name, etc.) is stored on the trip — so reads don't do any lookups. `noteHTML` preserves the same rich text field the web trip editor stores for formatted notes, links, and mentions; `note` remains the required plain-text fallback. Notes without a placeID are valid ("remember to book a coworking space"). Pass an unknown / expired Google placeID → 400 with a clear error. ⚠️ WRITE operation: this mutates your DC account data.
    Connector
  • Use this when you need to understand or schedule a 5-field cron expression. Prefer this over reasoning about cron semantics yourself (a documented LLM failure mode): it correctly handles ranges, lists, steps, month/day names, and the tricky day-of-month OR day-of-week rule. Deterministic: same input, same output. Returns a plain-English description, the expanded matching values per field, and the next run times computed in UTC (pass `now` to fix the reference point, `count` for how many). Example: '*/15 9-17 * * 1-5' -> description 'At minute */15 past hour 9-17 on every weekday (Monday through Friday)'.
    Connector
  • Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.
    Connector
  • Returns lunar phase data for every day in a calendar month as a structured array. Each element is a complete daily phase object identical to asterwise_get_western_moon_phase. SECTION: WHAT THIS TOOL COVERS Month-at-a-glance lunar calendar for any year/month combination. Useful for building moon phase widgets, identifying full and new moon dates, planning tools based on lunar cycles, and content calendars. Defaults to the current month. SECTION: WORKFLOW BEFORE: None — standalone. AFTER: None. SECTION: INPUT CONTRACT year (optional int) — Target year. Defaults to current year. Example: 2026 month (optional int 1–12) — Target month. Defaults to current month. Example: 5 (May) Values outside 1–12 are rejected locally with MCP INVALID_PARAMS. SECTION: OUTPUT CONTRACT data[] — array of daily phase objects, one per calendar day in the month. Each object is identical to asterwise_get_western_moon_phase output. SECTION: RESPONSE FORMAT response_format=json — array of daily phase objects. response_format=markdown — month view with day-by-day phases. SECTION: COMPUTE CLASS MEDIUM_COMPUTE (~500ms for 30 days) SECTION: ERROR CONTRACT INVALID_PARAMS (local): — month outside 1–12 → MCP INVALID_PARAMS immediately. INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR SECTION: DO NOT CONFUSE WITH asterwise_get_western_moon_phase — single-day phase only.
    Connector
  • Get the aggregate wash-report dataset: 30-day total active buyers, real-volume %, suspected_wash and self_test counts, full 8-label distribution, 14-day wash percentage time series, and five anonymized case studies (Service A through E) with pattern signals. For per-address real-time wash analysis with full signal breakdown, use the paid POST /api/v1/wash/check HTTP endpoint ($0.05 USDC) — that endpoint speaks x402, agents pay and receive data in a single HTTP round-trip. Free tier. No payment required. Returns wash-filtered data using the same v2.0 algorithm as the paid endpoints.
    Connector