Skip to main content
Glama
RyanCardin15

noaa-tidesandcurrents-mcp

get_high_tide_flooding_daily

Retrieve daily high tide flooding counts by station, specifying flood threshold, date range, and output format (json, xml, csv) for accurate coastal flood analysis.

Instructions

Get high tide flooding daily 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

  • Zod schema defining the input parameters and validation for the get_high_tide_flooding_daily tool.
    export const HighTideFloodingDailySchema = 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 daily count data');
  • Registers the get_high_tide_flooding_daily tool with the FastMCP server, specifying name, description, input schema, and a thin execute handler that delegates to the DpapiService.
    server.addTool({
      name: 'get_high_tide_flooding_daily',
      description: 'Get high tide flooding daily count data for a station',
      parameters: HighTideFloodingDailySchema,
      execute: async (params) => {
        try {
          const result = await dpapiService.getHighTideFloodingDaily(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get high tide flooding daily data: ${error.message}`);
          }
          throw new Error('Failed to get high tide flooding daily data');
        }
      }
    });
  • Core handler in DpapiService that constructs the API request to NOAA's Derived Product API endpoint '/htf/daily' and fetches the high tide flooding daily data.
    /**
     * Get high tide flooding daily count data
     * @param params Parameters including station ID, date range, and thresholds
     * @returns Daily flood count data
     */
    async getHighTideFloodingDaily(params: Record<string, any>): Promise<any> {
      const { station, format = 'json', ...rest } = params;
      
      return this.fetchDpapi('/htf/daily', {
        station,
        format,
        ...rest
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'gets' data (implying read-only), but doesn't disclose rate limits, authentication needs, data freshness, or what 'count data' entails (e.g., aggregated values). For a data retrieval tool with 7 parameters, this leaves significant gaps in understanding its operation.

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, efficient sentence that front-loads the core purpose without wasted words. It directly communicates the tool's function in a compact form, making it easy to parse.

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

Completeness2/5

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

For a tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'daily count data' returns (e.g., time series, totals), how parameters like 'datum' or 'threshold' affect results, or error conditions. Given the complexity and lack of structured metadata, more context is needed for effective use.

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 fully documents all 7 parameters with descriptions and enums. The description adds no parameter-specific information beyond implying a 'station' is required. Baseline 3 is appropriate as the schema does the heavy lifting, though the description doesn't compensate with additional context like parameter interactions.

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 as 'Get high tide flooding daily count data for a station', specifying the verb ('Get'), resource ('high tide flooding daily count data'), and target ('for a station'). It distinguishes from siblings like get_high_tide_flooding_annual by specifying 'daily' granularity, though it doesn't explicitly contrast with other flooding tools like monthly or seasonal.

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. It doesn't mention sibling tools like get_high_tide_flooding_monthly or get_high_tide_flooding_annual, nor does it specify prerequisites or context for choosing daily data over other timeframes.

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