Skip to main content
Glama

Supersurf

Search surf spots

search_surf_spots
Read-onlyIdempotent

Use this when the person names a surf spot, a town or a country and you need the spot's id. country is a two-letter code (PT) to keep to one country. Not for spots near a place: use list_surf_spots_near. Answers surf spots whose name, town, area or country match the words in any order, plurals, case or a typo: each with its id, name, town, country, kind (beach break, reef, point) and which way it faces; the closest names when nothing matches; at most 50.

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": {
      "query": "<query>"
    },
    "name": "search_surf_spots"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
countryNoa two-letter country code: PT, FR, US

Output Schema

NameRequiredDescriptionDefault
spotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond them by disclosing matching tolerance (any word order, plurals, case, typos), the fallback to closest names when nothing matches, and a hard 50-result ceiling. It stops short of describing ranking order among successful matches or what the id looks like, which keeps it off a 5.

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 usage condition and the exclusion are front-loaded where an agent will read them first, and there is no filler. The final sentence is a long run-on that packs matching rules, return fields and fallback behavior into one clause chain, which costs some scannability.

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?

An output schema exists, so the description need not document return values, and it still summarizes them briefly. For a three-parameter, single-required search tool, the routing guidance, matching semantics, fallback behavior and result cap together cover everything an agent needs to call it correctly.

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 33%, so the description must compensate, and it largely does: it explains what query matches against (name, town, area, country) and that country is a two-letter code scoped to one country, plus the 50 cap that bounds limit. It never states what limit actually does (cap the number of returned spots) as distinct from the result ceiling, leaving that parameter to inference.

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 first sentence names a specific verb (search) plus the resource (surf spots) and states the concrete outcome the agent needs: the spot's id. It also implicitly distinguishes itself from proximity-based siblings by framing the lookup as name/town/country matching, and explicitly names the sibling it is not.

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?

It gives both sides of the routing decision: use this when the person names a spot, town or country; do not use it for spots near a place, and use list_surf_spots_near instead. The alternative is named with the exact condition that selects it, leaving nothing 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