Finnish Meteorological Institute open data (forecast, observations, warnings)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 35 tools
Most tools have detailed, distinct descriptions, but there is real overlap: ask_pipeworx, ask_pipeworx_beta (explicitly identical to the stable router right now), ask_pipeworx_grounded, and deep_research all serve overlapping 'answer a question' purposes, and discover_tools vs suggest_questions both orient the caller. The polymarket_arbitrage / polymarket_edges / polymarket_edge_tracker trio also blurs (scan vs. scan vs. history), and ai_visibility_check vs scan_competitor_ai_presence differ only by single-vs-multi entity.
Names are overwhelmingly snake_case verb_noun (ai_visibility_check, compare_entities, resolve_entity, validate_claim, list_subscriptions), which is predictable. Minor deviations: bare verbs (forecast, remember, recall, forget, subscribe) and a family of ask_pipeworx* / polymarket_* names where the suffix carries the distinction rather than the verb.
35 tools is well over the comfortable 3-15 range and heavy even for a gateway, and the count is inflated by near-redundant entries (three ask_pipeworx variants, two discovery/onboarding tools, a five-tool polymarket cluster). Several tools (pipeworx_feedback, pipeworx_trending, generate_llms_txt, scan_dependency) are tangential to the apparent weather/data domain, making the surface feel bloated rather than scoped.
Lifecycle coverage is largely present: memory (remember/recall/forget), subscriptions (subscribe/list_subscriptions/unsubscribe/recent_alerts), and the core weather surface (forecast, latest_observations, recent_observations, warnings) are all covered. Minor gaps remain — no update/edit for stored memory beyond overwrite, no way to list or manage alerts config beyond cancel — but agents can work around them.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."MET Norway weather (api.met.no behind yr.no) — global forecast, sunrise, ocean
Finland Open Data (www.avoindata.fi/data/en) CKAN MCP.
Finnish postal-area and municipality statistics; rank, compare, history, air quality, nearby places
Weather forecasts from MET Norway (Yr): geocoding plus hourly forecasts worldwide.
Add one secure layer between your agents and this server.