Skip to main content
Glama

Fmi

by io.github.pipeworx-io

Warnings

warnings
Read-onlyIdempotent

Active FMI weather warnings for Finland (thunderstorm, wind, rain, snow, cold, forest fire, sea) — English headline, severity, colour, valid-from/to and the affected regions for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1-100 (default 25).
severityNoFilter by CAP severity: Minor | Moderate | Severe | Extreme.
include_expiredNoInclude warnings whose validity window has already passed (default false).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNo
returnedNo
warningsNo
active_countNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / active_count
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / body
      Removed value: -{
-  "description": "ISO bulletin XML content as text",
-  "type": "string"
-}
    • removedOutput schema / properties / format
      Removed value: -{
-  "description": "Data format",
-  "enum": [
-    "xml"
-  ],
-  "type": "string"
-}
    • addedOutput schema / properties / returned
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / source
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / warnings
      Added value: +{
+  "items": {
+    "properties": {
+      "areas": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "certainty": {
+        "type": "string"
+      },
+      "color": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "event": {
+        "type": "string"
+      },
+      "expires": {
+        "type": "string"
+      },
+      "headline": {
+        "type": "string"
+      },
+      "onset": {
+        "type": "string"
+      },
+      "probability_pct": {
+        "type": "number"
+      },
+      "severity": {
+        "type": "string"
+      },
+      "typical_impacts": {
+        "type": "string"
+      },
+      "updated": {
+        "type": "string"
+      },
+      "urgency": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "format",
-  "body"
-]
  2. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {}
-]New value: +[
+  {},
+  {
+    "limit": 10,
+    "severity": "Moderate"
+  }
+]
    • addedInput schema / properties / include_expired
      Added value: +{
+  "description": "Include warnings whose validity window has already passed (default false).",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "1-100 (default 25).",
+  "type": "number"
+}
    • addedInput schema / properties / severity
      Added value: +{
+  "description": "Filter by CAP severity: Minor | Moderate | Severe | Extreme.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "description": "ISO bulletin XML content as text",
+      "type": "string"
+    },
+    "format": {
+      "description": "Data format",
+      "enum": [
+        "xml"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "format",
+    "body"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds specific behavioral details: only active warnings, output attributes, and the implication that expired warnings are excluded (default false). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence efficiently communicates the tool's purpose and output details without redundancy. The list of warning types and field names is compact and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool, full schema coverage, and the presence of an output schema, the description is complete. It covers the domain, scope, data source, and output attributes, while the schema and annotations handle the remaining operational details.

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 coverage is 100%, with each parameter fully described. The description adds no new parameter-level information beyond what the schema already provides, though it reinforces the 'active' default through the word 'Active'. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides 'Active FMI weather warnings for Finland' and enumerates specific warning types and output fields (headline, severity, colour, validity, regions). This verb-like noun phrase with detailed scope clearly differentiates it from sibling tools like forecast or observations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving current warning status but does not explicitly name alternatives or provide when-not-to-use guidance. The 'Active' qualifier gives clear context, but there is no direct comparison to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fmi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools are well-differentiated, with detailed descriptions clarifying their distinct purposes. However, there is some overlap between the multiple 'ask' tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, suggest_questions) and between weather tools (forecast, latest_observations, recent_observations, warnings), which could cause confusion. Overall, ambiguity is low.

Naming Consistency5/5

All 34 tool names follow a consistent lowercase_with_underscores (snake_case) pattern. Names are descriptive and predictable, such as 'ask_pipeworx', 'entity_profile', 'polymarket_arbitrage', etc. No mixing of conventions like camelCase or inconsistent verb styles.

Tool Count3/5

The server has 34 tools, which is on the higher side given its broad scope covering weather, company research, prediction markets, and general data queries. While not excessive, it could be split into more focused servers for clarity. The count feels a bit heavy but still manageable.

Completeness4/5

The tool set covers a wide range of data domains (weather, company financials, prediction markets, news, memory, subscriptions) with reasonable completeness. Minor gaps exist, such as limited weather coverage (Finland only) and no direct support for non-company entities or unofficial data sources, but core workflows are well-supported.

Resources