Skip to main content
Glama
RyanCardin15

LocalTides MCP Server

get_top_ten_water_levels

Retrieve the top ten highest or lowest water levels for a specific station using JSON, XML, or CSV formats, with options for datum reference and unit preferences. Facilitates analysis of water level data on the LocalTides MCP Server.

Instructions

Get top ten highest or lowest water levels for a station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
analysis_typeNoAnalysis type (highest or lowest)
datumNoDatum reference for DPAPI
formatNoOutput format (json, xml, csv)
stationYesStation ID
unitsNoUnits to use ("english" or "metric")

Implementation Reference

  • Implementation of getTopTenWaterLevels that fetches data from NOAA DPAPI /topten endpoint.
    async getTopTenWaterLevels(params: Record<string, any>): Promise<any> {
      const { station, format = 'json', ...rest } = params;
      
      return this.fetchDpapi('/topten', {
        station,
        format,
        ...rest
      });
    }
  • Zod input schema defining parameters for the get_top_ten_water_levels tool, including station, format, datum, units, and analysis_type.
    export const TopTenWaterLevelsSchema = z.object({
      station: StationSchema,
      format: FormatSchema,
      datum: DpapiDatumSchema,
      units: UnitsSchema,
      analysis_type: z.enum(['highest', 'lowest']).optional().describe('Analysis type (highest or lowest)')
    }).describe('Get top ten water levels for a station');
  • Tool registration in FastMCP server, specifying name, description, input schema, and execute handler that calls the service method.
    server.addTool({
      name: 'get_top_ten_water_levels',
      description: 'Get top ten highest or lowest water levels for a station',
      parameters: TopTenWaterLevelsSchema,
      execute: async (params) => {
        try {
          const result = await dpapiService.getTopTenWaterLevels(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get top ten water levels: ${error.message}`);
          }
          throw new Error('Failed to get top ten water levels');
        }
      }
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description doesn't address important behavioral aspects like rate limits, authentication requirements, error conditions, or what format/scope the 'top ten' results represent (historical? real-time?). This leaves significant gaps in understanding how the tool behaves.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a tool with clear parameters documented elsewhere, and the information is front-loaded with no wasted verbiage.

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 moderate complexity (5 parameters, no output schema, no annotations), the description is minimally adequate but leaves important gaps. It identifies what the tool does but doesn't provide context about when to use it, behavioral characteristics, or output expectations. For a tool that presumably returns data, the lack of output schema means the description should ideally provide more guidance about what gets returned.

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 schema has 100% description coverage, so all parameters are documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions. It mentions 'highest or lowest' which corresponds to the 'analysis_type' parameter, but this is already covered in the schema's enum description.

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 with a specific verb ('Get') and resource ('top ten highest or lowest water levels for a station'). It distinguishes from some siblings like 'get_water_levels' by specifying the 'top ten' aspect, but doesn't explicitly differentiate from 'get_extreme_water_levels' which might serve a similar purpose.

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 when this tool is appropriate compared to other water level tools like 'get_water_levels' or 'get_extreme_water_levels', nor does it specify any prerequisites or exclusions for usage.

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-TidesAndCurrents-MCP'

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