Skip to main content
Glama

Supersurf

List surf spots near a place

list_surf_spots_near
Read-onlyIdempotent

Use this when the person asks what surf spots are around a place or around them. Give near (a town, area or spot name) or lat and lon. Not for where the surf is best: use find_best_surf. Answers the nearest surf spots to a spot, town or area named in near, or to lat and lon: each with its distance in km, kind and which way it faces; at most 40.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_surf_spots_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
nearNoa town, a coast or a spot: Lisbon, Hossegor, Supertubos
limitNo

Output Schema

NameRequiredDescriptionDefault
nearYes
spotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety burden is covered. The description goes beyond that by disclosing the output shape (distance in km, kind, facing) and a hard cap of at most 40 results, which is real behavioral context. It omits ordering guarantees or what happens when both 'near' and lat/lon are supplied.

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 use trigger is front-loaded, followed by the input rule and then the answer shape, which is the right order. There is mild redundancy between the opening clause and the later 'Answers the nearest surf spots... named in near, or to lat and lon' sentence, but no filler.

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?

Given four optional parameters, an output schema, and full annotations, the description covers the trigger, the input alternative, the result shape, and the cap. The one real gap is precedence when both 'near' and lat/lon are provided, which matters for a tool with zero required parameters.

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 description coverage is only 25%, with just 'near' documented, so the description must carry weight — and it does: it explains that 'near' takes a town, area, or spot name and that lat/lon are an alternative input route, an either/or relationship the schema does not express. 'At most 40' also gives the meaning of the limit bound. It adds no detail on what limit defaults to.

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 description states a specific verb and resource ('what surf spots are around a place or around them') and later makes the return explicit ('the nearest surf spots... each with its distance in km, kind and which way it faces'). It names the sibling find_best_surf as the different tool, so an agent can separate the two without opening schemas.

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?

It gives an explicit use condition ('when the person asks what surf spots are around a place') and an exclusion with a named alternative ('Not for where the surf is best: use find_best_surf'). It does not, however, distinguish this from the sibling search_surf_spots, which is a plausible source of mis-selection.

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