Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__ncei_station_search

Find NOAA weather stations inside a bounding box that actually hold data for a given dataset and date range, with each station's period of record and which elements it reports. Use this to get the station id that ncei_daily_summaries needs. Sourced from the NOAA NCEI search service.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bbox": "-118.7,33.7,-117.9,34.5",
      "limit": 5,
      "dataset": "daily-summaries",
      "endDate": "2026-03-01",
      "startDate": "2026-01-01"
    },
    "name": "noaa-ncei__ncei_station_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxYesBounding box "minLon,minLat,maxLon,maxLat" (WGS84). Reordered to NCEI's north,west,south,east form for you.
limitNoMax stations to return (default 25, max 200)
datasetNoDataset id (default "daily-summaries")
endDateNoLatest date the station must cover, YYYY-MM-DD
dataTypesNoComma-separated element codes the station must report, e.g. "TMAX,PRCP"
startDateNoEarliest date the station must cover, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose a non-obvious behavioral trait: results are filtered to stations that actually have data for the specified dataset and date range, not merely stations within the box. It also previews the per-station payload (period of record, elements) and the upstream source. Gaps remain around result ordering, pagination, and error/failure behavior when no stations qualify.

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?

Three sentences, each load-bearing: what it finds, why an agent should call it, and where the data comes from. The primary capability and the filtering constraint are front-loaded, and there is no filler.

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 six parameters, no annotations, and no output schema, the description does the right things: it explains the coverage filtering and summarizes the returned per-station fields so the agent needn't guess at return values. It is slightly incomplete on pagination and behavior when the bbox yields nothing, but the essentials for correct invocation are present.

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 parameters are already well documented, including the bbox coordinate ordering and the default/max limit. The description adds meaning by framing dataset and date range as coverage constraints rather than simple filters, but it repeats no syntax details and leaves dataTypes and limit to the schema, 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?

The description opens with a specific verb and resource ('Find NOAA weather stations') and immediately narrows scope to those inside a bounding box that actually hold data for the given dataset and date range. It also states what each result carries (period of record, reported elements), so the tool's output intent is clear without opening the schema.

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 explicitly names the downstream use case: get the station id that ncei_daily_summaries needs, which is strong routing guidance for an agent building a workflow. It stops short of stating when NOT to use it or which sibling to pick for other station-metadata needs, so it falls just under a 5.

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.