Surf MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tidesB | Get tide information for a specific location and date. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving tide information for a specific location and date, making it distinct by default.
The single tool follows a clear verb_noun pattern (get_tides), which is consistent and predictable. Since there are no other tools to compare against, the naming convention is perfectly uniform.
A single tool is too few for a server named 'Surf MCP Server', which implies a broader scope related to surfing or ocean conditions. This minimal toolset feels incomplete and under-scoped for the apparent domain.
The tool surface is severely incomplete for a surfing-related server. While get_tides covers tide information, there are obvious gaps such as wave forecasts, weather data, or surf spot details, which are essential for the domain and will likely cause agent failures.