Skip to main content
Glama

Supersurf

List surf schools

list_surf_schools
Read-onlyIdempotent

Use this when the person asks for lessons, a board to rent or a surf shop near a spot. kind keeps to one: school, rental or shop. Not for the waves: use get_surf_forecast. Answers surf schools, board rentals and surf shops within 2 km of a spot, each with its name, kind, distance, address and link where known, from Apple Maps' places.

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": "list_surf_schools"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
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
spotYes
placesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and a closed-world scope, so the safety profile is handled in structured data. The description still adds real behavioral context the annotations lack: a 2 km radius limit, the Apple Maps data source, and hedge words ('where known') implying some fields may be absent. It does not state result caps or empty-result behavior, keeping it below 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?

Three tight sentences: trigger, parameter note, exclusion. Everything earns its place and the usage guidance is front-loaded. Minor awkwardness in 'kind keeps to one' slightly reduces immediate parseability.

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 an output schema, the description covers the essentials: what is returned, the 2 km radius, the data source, the single-kind filter, and the sibling to use instead. Return field details are correctly left to the output schema. Only the behavior when kind is omitted and any result-count limits are unaddressed.

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 50% — 'spot' is documented in-schema but 'kind' is not. The description compensates by explaining that kind selects a single category among school, rental and shop, which clarifies the enum's filtering semantics. It does not explain what happens when kind is omitted (return all three?), leaving one small gap.

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 pair ('answers surf schools, board rentals and surf shops') and adds scope: within 2 km of a spot, sourced from Apple Maps places. It explicitly distinguishes itself from get_surf_forecast ('Not for the waves'), so an agent can route correctly without opening either 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?

Opens with the triggering user intent ('when the person asks for lessons, a board to rent or a surf shop near a spot'), which is exactly the decision boundary an agent needs. It also names the exclusion and the correct alternative ('Not for the waves: use get_surf_forecast'), covering when-to-use and when-not-to-use.

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