Skip to main content
Glama

Supersurf

Get a surf forecast

get_surf_forecast
Read-onlyIdempotent

Use this when the person asks about the waves, wind or conditions at one spot. Not for comparing spots: use find_best_surf. Not for tides: use get_tide_times. Answers one spot's forecast: now, its next good window, each of the next days (at most 16) with its best hours, and hour by hour the wave height, swell period and direction, wind speed and direction (offshore or onshore at this spot), and sunrise and sunset; each number names its source and when it was made.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spot": "<spot>"
    },
    "name": "get_surf_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
spotYesa surf spot's id as search_surf_spots or list_surf_spots_near show it, or its name (Ericeira, Supertubos, Hossegor)

Output Schema

NameRequiredDescriptionDefault
nowYes
daysYes
nextNo
spotYes
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is fully covered. The description adds the 16-day horizon and the fact that each number carries its source and timestamp, which is useful context. However, it says nothing about cost, rate limits, caching, or failure behavior for an unknown spot name, so it stops short of rich behavioral disclosure.

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?

Front-loaded with the use case and exclusions before the return-value detail, which is the right ordering. The final sentence is a long comma-chained list of outputs but every element is substantive, so it earns its length despite being dense.

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

Completeness4/5

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

For a two-parameter read tool with full annotations, the definition covers selection, scope and output shape adequately. Its main gap is the unanswered default for the optional days parameter; the return-value detail is arguably redundant given an output schema exists, but it is not harmful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: spot is documented in the schema with id-or-name examples, while days has no schema description. The description compensates partly by stating the horizon is "at most 16" days, clarifying what days controls. It never states the default when days is omitted, which is the one thing an agent most needs for that parameter.

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?

States a specific verb and resource ("get a surf forecast") and pins the scope to a single spot: "Answers one spot's forecast." It also explicitly names the siblings it is not (find_best_surf for comparing, get_tide_times for tides), so an agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit use condition ("when the person asks about the waves, wind or conditions at one spot") plus two explicit when-not rules routing to find_best_surf and get_tide_times. Nothing about tool selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources