Surf Session Finder
Server Details
Surf park sessions schedule availability and notifications for wave park surfers worldwide
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 3 of 3 tools scored.
Each tool has a clear, distinct purpose: list_pools retrieves pools, get_session_levels provides difficulty levels for a pool, and find_sessions returns available sessions. There is no functional overlap between them.
All tool names follow a consistent verb_noun pattern in snake_case (list_pools, get_session_levels, find_sessions), making them predictable and easy to use.
Three tools are appropriate for the scope of finding surf sessions: discover pools, get levels, and search sessions. The count feels lean but complete.
The tool set covers the essential workflow: listing pools, retrieving levels, and searching sessions. The booking URL in find_sessions externalizes booking, which is reasonable. A minor gap is the lack of a tool to fetch detailed info for a specific session, but it's not critical.
Available Tools
3 toolsfind_sessionsAInspect
Find available surf sessions at a pool. Returns date, time, skill level, available spots, and a booking URL. Filter by level, minimum spots, or time window.
| Name | Required | Description | Default |
|---|---|---|---|
| levels | No | Filter to specific level names (e.g. ["Beginner"]). Omit to return all levels. | |
| pool_id | Yes | Pool ID — use list_pools to get valid values | |
| min_spots | No | Minimum available spots required (default: 0) | |
| hours_ahead | No | Search window in hours from now (default: 192 = 8 days) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the returned fields (date, time, skill level, spots, booking URL) and filtering options, but does not mention any behavioral traits like rate limits, destructive actions (likely none), or authentication needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the primary purpose, and every sentence adds value. No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description specifies the returned fields. The tool has low complexity (4 params, 1 required) and the description covers essentials without gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 all parameters. The description adds a summary of filters ('Filter by level, minimum spots, or time window') but does not add new meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Find available surf sessions at a pool' – a specific verb and resource. It distinguishes from sibling tools get_session_levels (which retrieves levels) and list_pools (which lists pools).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusion criteria. However, the context of sibling tools and the description's clarity imply its use for session searching.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_session_levelsAInspect
Get the available session difficulty levels for a surf pool (e.g. Beginner, Intermediate, Advanced). Use the level names with find_sessions.
| Name | Required | Description | Default |
|---|---|---|---|
| pool_id | Yes | Pool ID — use list_pools to get valid values |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description discloses it returns difficulty levels and references pool_id from list_pools. Does not mention authentication, rate limits, or any side effects. Basic but adequate for a read-only lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, no redundant words. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple single parameter, no output schema, and low complexity, the description fully covers usage. Instructions for obtaining pool_id and using results are present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with pool_id described. Description adds value by explaining the return type (difficulty levels) and usage context, going beyond schema details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets available session difficulty levels for a surf pool with examples (Beginner, Intermediate, Advanced). It distinguishes itself from siblings by explicitly mentioning integration with find_sessions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to use level names with find_sessions, providing clear context for when this tool is used as a preparatory step. Lacks explicit when-not-to-use but sufficient for simplicity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_poolsAInspect
List all supported surf pools worldwide with their IDs, names, and locations. Always call this first to get valid pool_id values for the other tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool returns a list of all pools with IDs, names, and locations. No side effects; adequate for a read-only list. Could mention if list is dynamic, but not critical.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first states purpose and output, second gives usage advice. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description is complete: it explains what the tool returns (IDs, names, locations) and why it's useful (to get pool IDs for other tools).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has no parameters, so description has nothing to add. Baseline score of 4 applies for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists all supported surf pools worldwide with IDs, names, and locations. It distinguishes itself from siblings (find_sessions, get_session_levels) by focusing on a different resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to call this first to get valid pool_id values for other tools, providing clear context on when to use it and its role as a prerequisite.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!