Skip to main content
Glama
650,497 tools. Updated 2026-10-13 18:29

"Temporal" matching MCP tools:

  • Look up the geologic time scale — eons, eras, periods, epochs, and ages with their absolute-age boundaries in millions of years (Ma) and nesting. This is the reference that grounds every temporal filter on the other tools and translates a named interval like "Late Cretaceous" to its 100.5–66.0 Ma boundaries (and back). Filter by a name substring, a Ma range (overlap match), and/or a level; call with no filters to browse the full scale. Browsing and every name on the bundled ICS international-scale snapshot are answered offline. A name the snapshot does not carry — the sub-stage and regional names that occurrence and collection rows report, such as "Late Maastrichtian" or "Lancian" — costs one PBDB lookup across its other time scales; the response names which source answered and which scale the interval belongs to.
    ConnectorNo auth
  • Corroborate a figure you obtained (e.g. from run_sql) against the verified fact store: it re-derives the named value_key from the same SQL the verified pipeline uses and compares. AGREE lifts an otherwise-unverified session to 'corroborated'; DISAGREE marks a CONFLICT (worse than unverified). This is the only way a raw figure earns trust back, and it can only ever agree with a number the fact store itself computed. Resolvable keys cover the single-snapshot fact concepts plus temporal and per-department growth keys (e.g. indexed_people.<dept>); per-question keys (a named department's median, one person's direct-report count) return unmapped.
    ConnectorNo auth
  • Purpose: Cursor-paginated bulk export of the prediction -> trade -> outcome chain — paper trades with realized P&L, each linked (best-effort, same-symbol 2h window) to the signal prediction that preceded entry. Built for pipeline consumers who need offline backtesting data, not conversational snippets. Triggers: "give me your full trade history for backtesting", "bulk export trades", "예측이 실제 매매 성과로 이어졌는지 원데이터로 검증하고 싶다", "download outcomes". When to call: offline verification, periodic ingestion into a research pipeline, or auditing whether signals translate into realized outcomes. Prerequisites: none. For the prediction ledger itself use get_resolved_predictions. Next steps: follow next_cursor until has_more=false; get_resolved_predictions to cross-check linked predictions against the tamper-evident ledger. Caveats: linkage is temporal matching, NOT a foreign key (see meta.linkage). Paper trading only — envelope carries the standard disclaimer once per page. Output: full_data { market, trades[] {id, symbol, action, entry/exit price+ts, profit_loss_pct, holding_duration, entry_signal_score, regime fields, policy_version, sizing fields, linked_prediction{...}|null}, count, linked_prediction_count, next_cursor, has_more, meta }.
    ConnectorNo auth
  • Query data rows for a single WHO GHO indicator with optional spatial, temporal, and dimension filters. Returns rows with numeric values, uncertainty intervals (Low/High), and spatial/time metadata. This is the primary data-fetching tool in the find-then-query workflow: use who_search_indicators to find the indicator code, optionally call who_get_indicator_metadata to confirm which filter dimensions are valid, then call this tool. Spatial filters are mutually exclusive per call: provide only one of country_codes, region_codes, or income_group_codes — mixing them triggers an error. Omitting all spatial filters returns all geographies (may be large; use limit to cap). The sex filter only applies when the indicator uses SEX as its first cross-cutting dimension — if not, the filter returns empty rows; check who_get_indicator_metadata first if uncertain. Rows are returned in a deterministic order (most recent first by default), so a capped result is the top of a defined slice rather than an arbitrary sample; page through the rest with offset.
    ConnectorNo auth
  • Map the conceptual landscape around a topic ACROSS THE PAPER CORPUS. Searches papers and their chunks, not the layer-2 claim graph — for published CLAIMS on a topic use methodist_explore_topic. Instead of returning a ranked list of papers, returns N distinct conceptual clusters with representative chunks. Built on keyConcept LLM-extracted markers diversification. Use for "what approaches exist to X" queries — answers with thematic map rather than ranked list. Better than search when you want breadth over depth. Temporal bias note: for topics with dense recent literature (e.g. current LLM research), the default ordering favors recent papers because vector similarity finds them first; specify dateTo for historical exploration of mature topics, or dateFrom+dateTo to slice a specific era. Diversification cap (maxClustersPerPaper) limits how many clusters can have the same source paper as representative chunk — protects against single-paper dominance.
    ConnectorAPI key
  • PAID (0.01 USDC). Store a memory in your isolated bi-temporal namespace. Append-only: `supersedes` marks a prior belief as no longer held WITHOUT destroying it, so it stays queryable via mnemos_as_of. `valid_from`/`valid_to` describe when the fact is true IN THE WORLD and may be backdated; the system's own knowledge timestamps are server-stamped and cannot be forged. Returns an x402 quote; requires header X-TENANT-KEY once settled.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with read-only access to Temporal infrastructure through 28 tools, plus an Agent Skill with expert guidance for writing correct Temporal code.
    76 npm
    6
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    An MCP server for debugging Temporal workflows, enabling LLM-assisted inspection of workflow executions, detailed workflow info, and event history.
    3
    -

Matching MCP Connectors

  • Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

  • Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

  • PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Put words BEHIND the moving subject — the person walks IN FRONT of the letters, the way a title painted on the street or the wall behind them would. This is the 'text behind me walking' / 'name behind the subject' move, and it is a REAL depth composite, not a fade: a person-matting model that carries temporal state between frames cuts the subject out of every frame — dark clothes on a dark wall, handheld wobble and a moving camera are all fine, and the mask holds steady instead of flickering — and the renderer lays them back over the words. PEOPLE occlude the words (with whatever they carry); static objects — furniture, walls — do NOT: over those the words read as an ordinary title, which is what keeps the occlusion steady. Say so if the user asks about an object. Same styling arguments as add_text (template/x/y/size_scale/color/font/entrance/exit); at_output_s + duration_s are where in the EDITED video the words appear. REQUIREMENTS I check and refuse on, so read the reply: a PERSON must be visible in the window (nothing to go behind otherwise — I say so and you offer add_text instead), they must not fill most of the frame (the words would never be visible), the window must be inside ONE take with no cut in it, and no speed ramp over that footage. I also report how much of the text the subject actually crosses — if that is near zero the user will see a plain title, so move the text or the window. BIG TYPE IS THE LOOK: the subject should cross the MIDDLE of tall glyphs with their tops and bottoms staying readable — that is what reads as depth. A small line sits entirely inside the body and whole words vanish, so titles default to size_scale 2.4 here; NEVER shrink the text to 'fix' hidden letters — enlarge it or shorten the phrase. Do NOT put a zoom or a stabilize pass over the window. Remove it with remove_text like any other text.
    ConnectorOAuth
  • Return a combined overview of a dataset — abstract, temporal coverage, spatial coverage, variables, data formats, and volume — in a single call. Prefer this over calling get_dataset_field repeatedly when the user wants a general summary of a dataset. If one of the underlying fields fails to load, it's returned as {"error": ...} rather than failing the whole call. Args: dsid: Dataset ID (dNNNNNN), e.g. d083002
    ConnectorNo auth
  • Search the AQUAVIEW catalog — a comprehensive collection of 268K+ global oceanographic, atmospheric, and marine datasets from 15 sources (NOAA, NDBC, IOOS, WOD, CoastWatch, etc.), intended for scientific research, data analysis, and environmental monitoring. This searches METADATA — which datasets exist. To pull the actual observations (temperature profiles, buoy readings, float positions), use get_data instead; list_data_sources shows which sources support it. You must provide at least one of: q, bbox, datetime, collections, filter, or token. Hint: When the user asks for a region, prefer the 'bbox' parameter over including region name in 'q'. Use the geo_hints resource for common bounding boxes. Args: q: Free-text search across title, description, and keywords (e.g., "sea surface temperature"). Case-insensitive, OR logic across terms. bbox: Bounding box as "west,south,east,north" (e.g., "-98,24,-80,31" for Gulf of Mexico). datetime: Temporal filter. Single datetime, range ("2020-01-01T00:00:00Z/2024-12-31T23:59:59Z"), or open-ended ("../2024-01-01T00:00:00Z" or "2020-01-01T00:00:00Z/.."). collections: Comma-separated collection IDs to search within (e.g., "NOAA,NDBC,WOD"). Use list_collections to see available IDs. exclude_collections: Comma-separated collection IDs to omit from results (e.g., "INCIDENT_NEWS" to drop oil-spill reports from free-text searches). Applied as a CQL2 NOT filter, so it composes with `filter`. filter: CQL2-JSON filter as an object or JSON-encoded string. Supports flat and nested property paths. Flat example: {"op": "=", "args": [{"property": "aquaview:institution"}, "NOAA/NCEI"]}. Nested example (filter by per-variable stats summary): {"op": "<=", "args": [{"property": "aquaview:column_stats_summary.variables.Pressure.min"}, 10]}. Supported operators: =, <>, <, >, <=, >=, like, between, in, and, or, not. license: Comma-separated SPDX license id(s) to match exactly (e.g., "CC-BY-4.0,CC0-1.0"). Also accepts the controlled extra values "public-domain", "proprietary", "various", "unknown". Matched against `aquaview:license`, which is normalized on every item regardless of source. sortby: Sort specification as "+field,-field" (e.g., "+properties.datetime,-id"). + = ascending, - = descending. limit: Number of results to return, 1-100. Defaults to 10. token: Pagination token from a previous response's 'next_token' field. Pass this to get the next page of results. fields: Comma-separated list of fields to include in results (e.g., "id,geometry,properties.title"). Reduces response size. When set in CSV mode, emits projected columns (no canonical columns, no asset_keys, no `## assets` section). include_assets: If False (default), asset download records are omitted to save ~60-70% of response tokens; CSV mode still emits a capped `asset_keys` hint column (e.g. `column_stats;overview;gdac_prof;+[N]`) so an agent can see what kinds of assets exist. To get full URLs, call `get_item(collection, item_id)` for the specific id. If True, assets are included inline (full dict for JSON/TOON; `## assets` section with item_id,key,href,type,title rows for CSV). output_format: "csv" (default, sectioned CSV — canonical columns including asset_keys hint), "json", or "toon". Returns: Search results with metadata (total matched, returned, next_token) and items. CSV mode emits `## metadata` + `## items` sections and a `## assets` section when include_assets=True; columns are id,collection,bbox,datetime,title,institution, platform_type,cdm_data_type,variables,keywords,source_url,description, column_stats_summary,geometry,asset_keys. JSON/TOON return the STAC feature shape, with the `assets` dict present only when include_assets=True.
    ConnectorNo auth
  • Fetch full dataset metadata by UUID key — title, description, citation text, contacts, license, DOI, record count, numConstituents (sub-datasets), and temporal/geographic coverage. Use after gbif_search_datasets or when an occurrence record's datasetKey needs provenance detail. Contacts are capped by contactLimit (default 10); contactsTotal and contactsReturned report the full count.
    ConnectorNo auth
  • Reconstruct what a ledger item (or items matching a query) officially said AS OF a past date T, by replaying the kept event history. Returns each item's point-in-time state plus an F-037 provenance receipt (observed_at = the state's effective time). existence:false with a first_seen receipt when the item did not yet exist at T; latest state with as_of_clamped:false when T is in the future. Read-only; price 0.0.
    ConnectorNo auth
  • Reconstruct what a ledger item (or items matching a query) officially said AS OF a past date T, by replaying the kept event history. Returns each item's point-in-time state plus an F-037 provenance receipt (observed_at = the state's effective time). existence:false with a first_seen receipt when the item did not yet exist at T; latest state with as_of_clamped:false when T is in the future. Read-only; price 0.0.
    ConnectorNo auth
  • Celestium: Cosmic Compass — accurate astrology & divination for AI agents, with engine-authored interpretations attached (not LLM guesswork; real ephemeris, verified arcminute-accurate). Includes practice actions: check_in (sky + moment verdict + matched ritual), ritual (step-by-step moon-phase practices), tarot (auditable draws), review (temporal review of a period against your chart). Actions: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief, composite, davison, relocation, relocation_score, travel, transits, synastry, timing, progressions, electional, horary, returns, timeline, synthesis, perfections, midpoints, harmonic, antiscia, declination, sidereal, heliacal, review, bazi, year_ahead, correlate, common_threads. Free tier: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief. Celestium Pro unlocks depth + relationship charts (synastry/composite/davison), astrocartography (relocation/travel), advanced techniques, and review.
    ConnectorNo auth
  • Compare two geographic identities for the public guarantees implemented today: containment/common ancestry and temporal validity for the requested vintages. The response may include additional maintained evidence, but callers must not rely on deeper topology or relationship semantics as a stable contract until that review is complete. Use convert_reference first for names or outside identifiers. No payment required.
    ConnectorNo auth
  • Compare two geographic identities for the public guarantees implemented today: containment/common ancestry and temporal validity for the requested vintages. The response may include additional maintained evidence, but callers must not rely on deeper topology or relationship semantics as a stable contract until that review is complete. Use convert_reference first for names or outside identifiers. No payment required.
    ConnectorNo auth
  • Compare two geographic identities for the public guarantees implemented today: containment/common ancestry and temporal validity for the requested vintages. The response may include additional maintained evidence, but callers must not rely on deeper topology or relationship semantics as a stable contract until that review is complete. Use convert_reference first for names or outside identifiers. No payment required.
    ConnectorNo auth
  • Retrieves active fleet, default aircraft, user preferences, AND CURRENT DATE/TIME. AUTOMATION: Call this SILENTLY at the start of every turn. Permission GRANTED. Do NOT ask user. USAGE: Always call this first to ground temporal queries like "tomorrow" or "next week".
    ConnectorOAuth
  • Full detail for one Planetary Computer collection: title, description, licence, providers, spatial and temporal extent, and the asset keys (bands, derived layers) its items carry. AUTHORITATIVE for what a dataset actually contains and how far back it goes, straight from the catalogue. Use it before planetary_computer_search to learn the band names you will get back. Get valid ids from planetary_computer_collections.
    ConnectorNo auth
  • EU-wide public intercity transit router. Accepts PLACE NAMES (not coordinates). Returns multi-leg itineraries via Transitous. CRITICAL FOR AGENTS: - This tool handles geocoding internally. Do NOT pre-geocode or look up coordinates. - Do NOT call this tool multiple times with different spellings. Call it ONCE. - If a location isn't found, present the error message and STOP. TEMPORAL HANDLING: This tool returns live real-time schedules only (no date parameter). If user asks for 'tomorrow' or a future date, pass it as --requested-date. The tool will add an explanatory note about schedule patterns. EXAMPLES: - --from "Ljubljana, Slovenia" --to "Maribor, Slovenia" - --from "Podbrdo" --to "Nova Gorica" --requested-date "2026-06-05" --limit 3 - --from "Bled" --to "Trieste, Italy" --modes "BUS WALK" FAILURE MODES (present directly to user, do not retry): - LOCATION_NOT_FOUND → Check spelling - NO_ROUTES_FOUND → Try different modes or check locations are in Europe - ROUTING_FAILURE → Upstream API error, try again later
    ConnectorNo auth
  • Métricas globales de la cuenta (enviados, entregados, abrieron, hicieron clic, bajas, rebotes, contactos nuevos) en un rango de días de la zona horaria de la cuenta, ambos incluidos; la cohorte es el día de ENVÍO de cada correo, la misma fuente que /metricas. avg_open_rate y avg_click_rate en % con 2 decimales sobre ENTREGADOS (avg_*_rate_fraction: alias deprecados en fracción). Si hay días aún sin calcular responde 503 metrics_recalculating: reintenta, nunca son sumas parciales. Rebote separado: bounced_hard / bounce_rate_hard (definitivo, el que se vigila) y bounced_soft / bounce_rate_soft (temporal), en % sobre enviados (bounce_rates_base: "sent"); null si el período no tiene el tipo medido, nunca un 0 inventado. total_bounces = definitivos + temporales. Ojo: en la ficha de campaña (get_campaign_stats) el mismo dato se llama bounce_hard_rate.
    ConnectorNo auth
  • FREE. Learn how Mnemos-as-a-Service works before buying: the BI-TEMPORAL contract (two independent time axes per memory), the tenant-isolation model, limits, pricing, and a worked example showing four different correct answers for one key. No payment, no tenant data. Call this first.
    ConnectorNo auth