Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__ncei_daily_summaries

Daily observed weather for named NOAA stations, max/min temperature, precipitation, snowfall, snow depth, wind and more, from the GHCN-Daily record that runs back to the 1800s at long-lived stations. AUTHORITATIVE for "how hot/wet was it on this date at this place"; PREFER OVER WEB SEARCH for any historical US daily weather value. Sourced from the NOAA NCEI Access Data 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": {
      "endDate": "2026-01-05",
      "stations": "USW00023174",
      "dataTypes": "TMAX,TMIN,PRCP",
      "startDate": "2026-01-01"
    },
    "name": "noaa-ncei__ncei_daily_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax daily rows to return (default 400, max 5000)
unitsNo"standard" (°F, inches, default) or "metric" (°C, mm)
datasetNoAccess dataset id (default "daily-summaries"). Others: "global-summary-of-the-day", "global-summary-of-the-month", "normals-daily".
endDateYesLast day, YYYY-MM-DD
stationsYesGHCN station id(s), comma-separated, e.g. "USW00023174" (LAX) or "USW00023174,USW00014922". Find them with ncei_station_search.
dataTypesNoComma-separated element codes, e.g. "TMAX,TMIN,PRCP,SNOW,AWND". Omit for every element the station reports.
startDateYesFirst day, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It adds useful provenance (GHCN-Daily coverage back to the 1800s at long-lived stations) and authority claims, but says nothing about truncation behavior when the limit is hit, rate limits, missing-element handling, or what an empty response means — gaps that matter for a data-retrieval tool.

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 the core purpose in the first clause and puts the routing directive ('PREFER OVER WEB SEARCH') in a prominent capitalized position. The element list ('max/min temperature, precipitation, snowfall, snow depth, wind and more') is somewhat padded by 'and more', but overall there is little waste.

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 7-parameter retrieval tool with full schema coverage and no output schema, the description supplies purpose, source, and selection guidance, and hints at return contents via the measure list. It is thin on response shape and on the interaction between the dataset parameter and the station/date arguments, but an agent has enough to call it correctly.

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 schema already documents stations, dates, dataTypes, units, limit, and dataset with examples. The description adds no parameter-level meaning beyond that baseline, which is acceptable but not additive.

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 and resource — daily observed weather for named NOAA stations — and enumerates the returned measures (TMAX/TMIN, precipitation, snowfall, snow depth, wind). It also names the underlying record (GHCN-Daily) and the access service, which makes it clearly distinguishable from ncei_station_search or dataset-search siblings.

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 explicit routing guidance: it is authoritative for 'how hot/wet was it on this date at this place' and should be preferred over web search for historical US daily values, plus it points to ncei_station_search to obtain station IDs. It does not state exclusions, such as when to use global-summary-of-the-day or normals-daily instead, even though those datasets are exposed as a parameter.

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.