Skip to main content
Glama
RyanCardin15

noaa-tidesandcurrents-mcp

get_high_tide_flooding_monthly

Retrieve monthly high tide flooding counts for a specific station using NOAA Tides and Currents data. Specify station ID, flood threshold, and date range to analyze flooding trends in JSON, XML, or CSV formats.

Instructions

Get high tide flooding monthly count data for a station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
begin_dateNoStart date (YYYYMMDD format)
datumNoDatum reference for DPAPI
end_dateNoEnd date (YYYYMMDD format)
formatNoOutput format (json, xml, csv)
stationYesStation ID
thresholdNoFlood threshold level
yearNoYear for analysis (YYYY format)

Implementation Reference

  • Core handler function in DpapiService that executes the logic for retrieving high tide flooding monthly data by making an API call to the NOAA DPAPI '/htf/monthly' endpoint.
    async getHighTideFloodingMonthly(params: Record<string, any>): Promise<any> {
      const { station, format = 'json', ...rest } = params;
      
      return this.fetchDpapi('/htf/monthly', {
        station,
        format,
        ...rest
      });
    }
  • Zod schema defining the input parameters and validation for the get_high_tide_flooding_monthly tool.
    // High Tide Flooding Monthly schema
    export const HighTideFloodingMonthlySchema = z.object({
      station: StationSchema,
      format: FormatSchema,
      datum: DpapiDatumSchema,
      threshold: ThresholdSchema,
      begin_date: z.string().optional().describe('Start date (YYYYMMDD format)'),
      end_date: z.string().optional().describe('End date (YYYYMMDD format)'),
      year: YearSchema
    }).describe('Get high tide flooding monthly count data');
  • Tool registration in derived product tools module, specifying name, description, input schema, and execute handler that wraps the DpapiService call and handles errors.
    server.addTool({
      name: 'get_high_tide_flooding_monthly',
      description: 'Get high tide flooding monthly count data for a station',
      parameters: HighTideFloodingMonthlySchema,
      execute: async (params) => {
        try {
          const result = await dpapiService.getHighTideFloodingMonthly(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get high tide flooding monthly data: ${error.message}`);
          }
          throw new Error('Failed to get high tide flooding monthly data');
        }
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves data but does not describe any behavioral traits such as rate limits, authentication requirements, error handling, or the structure of the returned data. For a data retrieval tool with no annotation coverage, this is a significant gap, warranting a score of 2.

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?

The description is a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand at a glance. This minimalistic approach earns a score of 5 for conciseness and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, no output schema, and no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavioral aspects, output format, or usage context. While the schema covers parameters well, the absence of annotations and output schema means the description should provide more context, resulting in a score of 3.

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?

The description does not add any parameter-specific information beyond what is already detailed in the input schema, which has 100% description coverage. It mentions 'for a station,' aligning with the required 'station' parameter, but provides no additional context on parameter usage, dependencies, or semantics. Given the high schema coverage, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Get high tide flooding monthly count data for a station.' It specifies the verb ('Get'), resource ('high tide flooding monthly count data'), and target ('for a station'), making the action and scope unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_high_tide_flooding_annual' or 'get_high_tide_flooding_daily,' which limits the score to 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for high tide flooding data (e.g., annual, daily, seasonal), there is no indication of the specific context or use cases for monthly data, nor any mention of prerequisites or exclusions. This lack of comparative guidance results in a score of 2.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RyanCardin15/NOAA'

If you have feedback or need assistance with the MCP directory API, please join our Discord server