Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__ncei_search_datasets

Browse the NOAA NCEI dataset catalogue, climate, marine, satellite, radar, paleoclimate and storm archives, with each dataset's period of record, formats, keywords and description. Use it to find which archive answers a question before pulling values. 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": {
      "text": "precipitation",
      "limit": 5
    },
    "name": "noaa-ncei__ncei_search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoFree-text search over dataset titles, descriptions and keywords, e.g. "precipitation", "hurricane", "sea ice"
limitNoMax datasets to return (default 10, max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool browses a catalogue and returns period of record, formats, keywords, and descriptions, but it does not mention ranking, pagination, authentication, rate limits, or error behavior.

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?

The definition is front-loaded with the core purpose and is reasonably compact. The first sentence is somewhat dense with archive domains, but no sentence is clearly wasteful.

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 low-complexity search tool with full schema coverage, the description explains the returned metadata and the intended discovery use case. Minor gaps such as result ranking are acceptable because the schema covers parameters and there is no output schema to explain.

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 both parameters are already documented with descriptions and constraints. The description does not add syntax, examples, or other meaning beyond what the schema provides.

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 specific verb and resource: browsing the NOAA NCEI dataset catalogue, and it lists the archive domains and returned metadata. It is clear what the tool does, but it does not explicitly distinguish itself from sibling dataset-search tools such as CoastWatch or NESO.

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?

The sentence 'Use it to find which archive answers a question before pulling values' gives a clear discovery-before-retrieval use case. It does not state when not to use this tool or name alternative search tools for other catalogues.

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.