Skip to main content
Glama
Sign In

Geo-Insights Environmental Data

by io.github.mathisvfr
OverviewDiscussionsAdmin

Check Data Freshness

get_data_freshness
Read-onlyIdempotent

Check how fresh the data is for each of the 10 sources.

Returns sources with latest_observation timestamp, age_seconds, and a
status classification: "fresh" (<1h), "stale" (<24h), "offline" (>24h),
or "unreachable" (query failed for that source).

Use this to verify data availability before querying readings, or to
monitor source health. Individual source failures are reported per-source
(status: "unreachable") rather than failing the entire call.

This is also the server's health check — if this tool works, the server
is operational.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_data_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
+  "FreshnessEntry": {
+    "properties": {
+      "age_seconds": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Age Seconds"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Error"
+      },
+      "latest_observation": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Latest Observation"
+      },
+      "source": {
+        "title": "Source",
+        "type": "string"
+      },
+      "source_attribution": {
+        "title": "Source Attribution",
+        "type": "string"
+      },
+      "status": {
+        "description": "One of: fresh (<1h), stale (<24h), offline (>24h), no_data, unreachable",
+        "title": "Status",
+        "type": "string"
+      }
+    },
+    "required": [
+      "source",
+      "source_attribution",
+      "status"
+    ],
+    "title": "FreshnessEntry",
+    "type": "object"
+  }
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / sources
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/FreshnessEntry"
+  },
+  "title": "Sources",
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "sources"
+]
    • changedOutput schema / title
      Previous value: -"get_data_freshnessOutput"New value: +"FreshnessResult"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing partial-failure semantics (individual sources report 'unreachable' instead of failing the whole call) and the exact age thresholds for each status. That partial-failure behavior is the key non-obvious trait for an agent. The readOnly/idempotent/openWorld profile is already covered by annotations, so no extra credit there.

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?

Front-loaded with purpose, then return shape, then usage, then the health-check note. Every sentence carries distinct information; the status threshold list is compact and the partial-failure note is not repeated.

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?

Zero-parameter read tool with an output schema and full annotation coverage. The description supplies the behavioral context the structured fields cannot: per-source failure isolation and the health-check signal. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate. It correctly spends no words on inputs and instead explains the output classification, which is the only semantics that matter here.

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?

States a specific verb and resource ('Check how fresh the data is for each of the 10 sources') and immediately enumerates the return fields and status vocabulary, so the agent knows exactly what comes back. It is clearly distinguishable from sibling reading tools like get_latest_readings, which return values rather than availability metadata.

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?

Gives concrete when-to-use guidance: verify data availability before querying readings, or monitor source health. It also flags the health-check use case. It stops short of naming the specific sibling tools it should precede, so the routing is implied rather than explicit.

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

All Geo-Insights Environmental Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources