Bob Research Tools

weather.forecast

Read-only

Returns current conditions and the National Weather Service 7-day forecast for one US latitude and longitude as {source, location, current, forecast_updated, forecast, notes}: nearest-station temperature, humidity, wind and pressure, then up to 14 forecast periods with temperature, chance of precipitation, wind and a summary, usually in 1 to 3 seconds. US government data, public domain; US points only. A forecast is an estimate. Read-only. Paid per call with x402; outside the US or if the service is unavailable the call fails and is not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "weather.forecast"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes	Latitude of a US point in decimal degrees, for example 32.78.
`lon`	Yes	Longitude of a US point in decimal degrees, for example -96.80.

Output Schema

Name	Required	Description
`notes`	No	Source and caveats.
`source`	Yes
`current`	No	Latest nearest-station observation, or null if none could be read.
`forecast`	Yes	Up to 14 forecast periods.
`location`	Yes	The point, nearest city and forecast office.
`forecast_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only and non-destructive, and the description still adds substantial context beyond them: expected latency (1–3s), paid-per-call x402 billing, no charge on failure, data provenance/public-domain status, and a caveat that a forecast is an estimate. The only remaining detail an agent might want is caching, which is minor.

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

Conciseness4/5

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

Front-loads what is returned and then layers cost, scope, and caveats with no filler sentences. It is a single dense run-on with semicolons rather than cleanly separated points, which slightly hurts scannability.

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?

Even though an output schema exists, the description still names the response envelope and forecast contents, and it covers cost model, geographic limits, failure behavior, and data freshness (forecast_updated). Nothing an agent needs to decide to call or interpret a call is missing.

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% with examples and bounds for both lat and lon, so the schema carries the parameter burden. The description only restates 'one US latitude and longitude' and adds the US-only constraint, which is not a per-parameter semantic. 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 verb (returns) and resource (current conditions + NWS 7-day forecast) with an explicit scope of one US latitude/longitude. It is clearly separable from the sibling weather.alerts, which would cover warnings rather than point forecasts.

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 a clear applicability condition ('US points only') and what happens outside it ('the call fails and is not charged'), which is genuinely useful routing information. It stops short of naming weather.alerts or any alternative for non-US points, so no explicit when-not-and-use-instead pairing.

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

All Bob Research Tools tools Inspect

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

Need Help?