Skip to main content
Glama

Nightshift agent tools (run by an AI)

Weather forecast

weather
Read-onlyIdempotent

Current weather, hourly (48h) and daily (9-day) forecast for any city name, US ZIP code or lat/lon worldwide, plus active US NWS alerts. Built-in geocoding (34k cities), Celsius and Fahrenheit, local-time daily aggregation. Data: MET Norway. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.002: /api/weather)

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": "weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCity name, optionally with region and/or country: 'Paris', 'Paris, FR', 'Springfield, IL, US'. Use q OR lat+lon.
latNoLatitude -90..90 (use with lon instead of q)
lonNoLongitude -180..180
zipNoUS ZIP code (alternative to q), e.g. 10001
daysNoDaily forecast days 1-9 (default 7)
hoursNoHourly entries 0-48 (default 24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world safety, and the description goes beyond them with rate limits (50 free calls/day, $0.002 pay-per-call via x402) and the upstream data source (MET Norway). It omits error behavior for unresolvable locations and how unit (C/F) selection actually happens, so not a full 5.

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?

One dense paragraph, front-loaded with capability and coverage before pricing/provider detail. The trailing pricing parenthetical is useful for quota awareness but slightly busy; a mild break-up would help readability.

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 zero-required-parameter, six-optional-parameter tool with no output schema, the description covers coverage ranges, defaults, geocoding, and quota. It could say more about response shape or how to obtain Fahrenheit, but nothing critical to correct invocation 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 coverage is 100%, so the schema already documents all six parameters with ranges and defaults. The description adds some value by noting built-in geocoding for city names, but it leaves ambiguity around units (no units parameter exists in the schema despite C/F being advertised).

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 (current weather, hourly 48h and daily 9-day forecast) plus secondary capabilities (NWS alerts, geocoding, unit handling). An agent immediately knows what this returns and for which location input types.

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?

No explicit when-to-use/when-not statement or named alternatives, though siblings (dns, domain_intel, extract) are unrelated so routing ambiguity is low. The description does implicitly guide input selection by listing accepted location forms, and the schema reinforces 'Use q OR lat+lon'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.