AgentIndex x402

Weather Forecast

weather

Read-onlyIdempotent

Current weather and a 3-day forecast for any city or lat/lon - temperature, humidity, wind, conditions. No account, no API key. Try GET /weather/sample.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude. Use with lon when you already have coordinates.
`lon`	No	Longitude. Use with lat when you already have coordinates.
`city`	No	City name (e.g. Paris, Tokyo). Preferred when you do not have coordinates.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`daily`	Yes
`query`	No
`current`	Yes
`location`	Yes
`x402_receipt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / city / description

Added value: +"City name (e.g. Paris, Tokyo). Preferred when you do not have coordinates."

addedInput schema / properties / lat / description

Added value: +"Latitude. Use with lon when you already have coordinates."

addedInput schema / properties / lon / description

Added value: +"Longitude. Use with lat when you already have coordinates."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "current": {
+      "type": "object"
+    },
+    "daily": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "location": {
+      "type": "object"
+    },
+    "query": {
+      "type": "string"
+    },
+    "x402_receipt": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "location",
+    "current",
+    "daily"
+  ],
+  "type": "object"
+}

AddedSep 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful access context — 'No account, no API key' — which tells the agent there is no auth prerequisite, but it says nothing about rate limits, units, or timezone handling.

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?

Two compact sentences, front-loaded with the resource and scope, followed by the access note and sample hint. No filler or redundancy.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. It covers purpose, inputs, and auth adequately, though it omits units, forecast timezone, and rate-limit behavior for an open-world network tool.

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% and each parameter already explains itself, including the lat/lon pairing and 'preferred when you do not have coordinates'. The description merely restates 'any city or lat/lon', so 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?

States a specific resource (weather) with explicit scope (current conditions plus a 3-day forecast) and enumerates the returned fields: temperature, humidity, wind, conditions. No sibling tool covers weather, so there is zero ambiguity about which tool to pick.

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

Usage Guidelines3/5

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

Usage context is implied (call it when you need weather for a city or coordinates) and it notes you can try GET /weather/sample, but it never states when to prefer lat/lon vs city or when not to use the tool. Guidance exists but is thin.

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

All AgentIndex x402 tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.