Skip to main content
Glama

Tomorrow Io

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Realtime

realtime
Read-onlyIdempotent

Get current/real-time weather conditions for a location — temperature, feels-like, humidity, wind, precipitation probability, cloud cover, UV index, and visibility. Location can be "lat,lon" coordinates or a city name. Example: realtime({ location: "new york", units: "imperial" }) or realtime({ location: "40.71,-74.01" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitsNoUnit system: "metric" (default) or "imperial"
_apiKeyNoTomorrow.io API key (optional — get a free one at tomorrow.io; if omitted the platform key is used)
locationYesLocation to look up — either "lat,lon" coordinates (e.g. "40.71,-74.01") or a city name (e.g. "new york", "london")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-tomorrow-io-api-key",
-    "location": "new york",
-    "units": "imperial"
-  },
-  {
-    "location": "40.71,-74.01"
-  }
-]New value: +[
+  {
+    "location": "new york",
+    "units": "imperial"
+  },
+  {
+    "location": "40.71,-74.01"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-tomorrow-io-api-key",
+    "location": "new york",
+    "units": "imperial"
+  },
+  {
+    "location": "40.71,-74.01"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond annotations by listing the data returned and showing accepted location formats and example invocations, which matters given there is no output schema.

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?

The description is compact and front-loaded: the core purpose and returned fields come first, followed by input formats and concrete examples. Every sentence earns its place, and there is no filler or repetition of annotation data.

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

Completeness4/5

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

For a simple read-only weather tool, the description plus a fully documented schema is nearly complete. It explains what data is returned, how location and units are specified, and gives examples. The main remaining gap is the absence of an output schema and any mention of error behavior, but the listed metrics compensate reasonably.

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 description coverage is 100%, so the schema already documents location, units, and _apiKey clearly. The description repeats the location format and adds an invocation example, but it does not introduce meaning that the schema does not already provide. Baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: 'Get current/real-time weather conditions for a location' and enumerates the exact returned fields. This is clear and usable, though it does not explicitly name or contrast with the 'forecast' sibling; the 'current/real-time' qualifier only implicitly distinguishes it.

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 clearly establishes that this tool is for current conditions rather than forecasts, giving an agent a solid cue about when to call it. However, it does not explicitly say 'use forecast for future conditions' or list exclusions, so it falls short of full alternative routing.

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

All Tomorrow Io 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