Skip to main content
Glama

Get NWS grid info

get_grid_info
Read-only

Look up National Weather Service grid metadata for a US place or coordinates to find the forecast office, grid cell, radar station, and forecast/county zones needed for further NWS API calls.

Instructions

The National Weather Service grid metadata for a US location: forecast office, grid cell, radar station, and forecast/county zones. Useful for understanding which office issues a forecast and for building further NWS API calls.

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_grid_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoUS place name to look up, as "City, ST" (e.g. "Tucson, AZ") or a full street address. Provide either this or latitude+longitude, not both.
latitudeNoLatitude in decimal degrees. Must be paired with longitude.
longitudeNoLongitude in decimal degrees. Must be paired with latitude.
response_formatNomarkdown for a compact human/LLM-readable summary, json for the structured object.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is supplied. The description adds the notable constraint that this covers US locations only, but says nothing about ambiguity handling in place resolution, error behavior for unknown places, or rate limits.

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 sentences, front-loaded with what the tool returns, then the practical reason to call it. No filler, no repetition of schema or annotation content.

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 no output schema, the description carries the return-value burden and does list the main returned fields, plus the US-only scope. It is adequate for a simple read-only lookup, though it could say more about what the response looks like in practice.

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 the schema already explains the place-vs-latitude/longitude exclusivity and the response_format enum. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a concrete resource (NWS grid metadata) and enumerates the specific fields returned: forecast office, grid cell, radar station, and forecast/county zones. That is enough to tell it apart from forecast/alert/conditions siblings, though it stops short of an explicit verb-plus-scope framing like 'look up the grid cell for a location'.

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?

It gives clear usage context: understanding which office issues a forecast, and building further NWS API calls. There are no explicit exclusions or named alternatives (e.g. 'use get_forecast instead for actual forecast values'), so it lands just below the top band.

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