Skip to main content
Glama
kykoay

BC Water Tides MCP Server

by kykoay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

plot_tide_forecast

Generate a tide height plot for any Canadian station and date, displaying water levels in PST with high/low tide markers and an optimal diving zone to aid marine activity planning.

Instructions

Generate a tide height plot showing water levels as a function of time in PST.

This tool creates a visual chart of tide heights throughout a specified day, with timestamps displayed in Pacific Standard Time (PST/PDT).

The plot includes:

  • Tide height curve with hourly data points

  • Highlighted high and low tide markers with annotations

  • Optimal diving zone indicator (low tide window)

  • Dark, ocean-themed styling

Returns:

  • Plot image (either saved to file or as base64 data)

  • High and low tide summary information

Use this tool when the user wants a visual representation of tide patterns for dive planning, fishing, boating, or other marine activities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesThe specific date to plot (format: YYYY-MM-DD). The plot will show tide heights for this entire day in PST.
titleNoOptional custom title for the plot. If not provided, uses default title with station name and date.
save_pathNoOptional file path to save the plot image. If not provided, returns base64-encoded image data.
station_nameYesThe name of the monitoring station (e.g., 'Point Atkinson', 'Campbell River', 'Victoria'). Partial matching is supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the behavioral burden and does so thoroughly: it discloses the PST/PDT timezone, hourly data points, high/low markers, diving-zone indicator, output modes (file or base64), and returned high/low summary. It also implies no destructive side effects beyond optional file saving.

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 description is well structured with bullets and front-loaded purpose, but the first two sentences are somewhat redundant: both state that it produces a tide-height chart over a day in PST/PDT. Minor repetition prevents a perfect score.

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

Completeness5/5

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

For a medium-complexity tool with no output schema, the description covers the return value (plot image and summary), save behavior, timezone, plot contents, and appropriate use cases. The agent has enough context to invoke it correctly and interpret its result.

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 already documents date, title, save_path, and station_name well. The description adds only generic context about 'the specified day' and 'optional' fields without explaining parameter behavior beyond the schema.

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

Purpose5/5

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

The opening sentence uses a specific verb ('Generate') and resource ('tide height plot'), and the description clearly distinguishes this from the sibling data-retrieval tools by emphasizing visual output. The plot's contents and styling make its purpose unambiguous.

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 final sentence gives concrete context for when to use the tool ('visual representation... for dive planning, fishing, boating'). It does not explicitly contrast with get_tide_forecast or get_tide_forecast_pst for cases where tabular data is needed instead of a plot.

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

Deploy Server

Other Tools