Skip to main content
Glama
RyanCardin15

LocalTides MCP Server

get_currents

Retrieve currents data for a specific station, specifying date range, time zone, and output format. Use this tool to access precise water current information in json, xml, or csv formats.

Instructions

Get currents data for a station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
begin_dateNoStart date (YYYYMMDD or MM/DD/YYYY)
binNoBin number
dateNoDate to retrieve data for ("today", "latest", "recent", or specific date)
end_dateNoEnd date (YYYYMMDD or MM/DD/YYYY)
formatNoOutput format (json, xml, csv)
rangeNoNumber of hours to retrieve data for
stationYesStation ID
time_zoneNoTime zone (gmt, lst, lst_ldt)
unitsNoUnits to use ("english" or "metric")

Implementation Reference

  • Core handler function that fetches currents data from NOAA API by setting product to 'currents' and calling the generic fetchDataApi method.
    async getCurrents(params: Record<string, any>): Promise<any> {
      return this.fetchDataApi({
        ...params,
        product: 'currents'
      });
    }
  • Zod schema defining input parameters for the get_currents tool, including station, date parameters, bin, units, etc., with refinement for date requirements.
    export const GetCurrentsSchema = z.object({
      station: StationSchema,
      date: DateSchema,
      begin_date: BeginDateSchema,
      end_date: EndDateSchema,
      range: RangeSchema,
      bin: BinSchema,
      units: UnitsSchema,
      time_zone: TimeZoneSchema,
      format: FormatSchema,
    }).refine(
      data => (data.date || (data.begin_date && data.end_date) || (data.begin_date && data.range) || (data.end_date && data.range) || data.range),
      { message: "You must provide either 'date', 'begin_date' and 'end_date', 'begin_date' and 'range', 'end_date' and 'range', or just 'range'" }
    );
  • Registration of the 'get_currents' tool in the MCP server, defining name, description, schema, and handler that delegates to NoaaService.getCurrents.
    const getCurrents: MCPTool = {
      name: "get_currents",
      description: "Get currents data for a station",
      inputSchema: GetCurrentsSchema,
      handler: async (params) => {
        return this.noaaService.getCurrents(params);
      }
    };
  • Alternative registration of the 'get_currents' tool using FastMCP server.addTool, with inline schema and execute handler wrapping NoaaService.getCurrents and returning JSON string.
    server.addTool({
      name: 'get_currents',
      description: 'Get currents data for a station',
      parameters: z.object({
        station: StationSchema,
        date: DateSchema,
        begin_date: BeginDateSchema,
        end_date: EndDateSchema,
        range: RangeSchema,
        bin: BinSchema,
        units: UnitsSchema,
        time_zone: TimeZoneSchema,
        format: FormatSchema,
      }).refine(refineDateParams, { message: dateRefinementMessage }),
      execute: async (params) => {
        try {
          const result = await noaaService.getCurrents(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get currents: ${error.message}`);
          }
          throw new Error('Failed to get currents');
        }
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action without details on permissions, rate limits, data freshness, or output format implications. It mentions 'data' retrieval but doesn't clarify if this is real-time, historical, or predictive, or what the response structure might be, leaving significant gaps for a tool with 9 parameters.

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 with zero wasted words, clearly front-loading the core action. It's appropriately sized for a tool where the schema handles most documentation, though it could benefit from additional context.

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?

Given the complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'currents data' includes, how results are structured, or usage context, forcing reliance on the schema alone. For a data retrieval tool with rich parameters, more descriptive context is needed to guide 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?

The description adds no parameter-specific information beyond the action, while the input schema has 100% description coverage with detailed parameter docs (e.g., date formats, enum values). Since schema coverage is high, the baseline is 3, as the description doesn't compensate but also doesn't detract from the well-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get currents data for a station' states the basic action (get) and resource (currents data for a station), but it's vague about what 'currents data' entails and doesn't differentiate from siblings like 'get_water_levels' or 'get_tide_predictions' that might retrieve related oceanographic data. It provides minimal but functional purpose information.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_water_levels' or 'get_tide_predictions' from the sibling list. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based solely on the tool name and parameters.

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