Skip to main content
Glama

RideMyPark

Taxonomie des spots RideMyPark

ridemypark_list_spot_features
Read-onlyIdempotent

Rend le vocabulaire exact des filtres du catalogue RideMyPark : les 41 modules (bowls, curbs, euro gap…), les 3 sous-types de spot et les 4 disciplines, chacun avec son slug d'API, son libellé français et ses synonymes acceptés.

Sert quand une recherche doit être filtrée précisément et que le terme employé par la personne n'est pas forcément un slug du catalogue (« un bol » désigne « bowls », « escaliers » désigne « stairs »).

Paramètres :

  • response_format ('markdown' | 'json') : défaut markdown.

Rend :

  • modules : liste de { slug, label, synonyms } — le slug est la valeur que l'API accepte ;

  • spot_types : les trois sous-types (street, skatepark, pumptrack) avec leur libellé ;

  • disciplines : skate, bmx, scooter, roller — les valeurs du filtre discipline de ridemypark_search_spots.

Limites connues des données :

  • Peu de fiches déclarent leur discipline. Le filtre discipline de la recherche retient aussi les spots qui portent un module adapté à la pratique : c'est l'API qui applique cette règle, la même pour le site et la CLI.

  • Les libellés français ne sont pas acceptés par l'API : elle compare des slugs. C'est la raison d'être des synonymes rendus ici.

Erreurs : aucune. Cet outil ne fait aucun appel réseau, la taxonomie est embarquée.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNomarkdown pour une réponse lisible, json pour les données brutes.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), it discloses that the tool makes no network call, that the taxonomy is embedded, and that no errors can occur. It also exposes real data limitations: few listings declare a discipline, and the API matches slugs rather than French labels, which explains why synonyms exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then parameters, then return shape, then data limits, then error behavior — clearly sectioned and easy to scan. Every block carries distinct information; nothing is padding.

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?

With no output schema, the description fully covers the return shape (slug/label/synonyms, the three spot types, the four discipline values). It also explains the API matching rule that would otherwise cause silent filter failures, which is exactly what an agent needs to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema coverage including the enum and its default, so the schema already does the work. The description restates response_format and its default without adding meaning beyond the schema, which is the baseline case.

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 names a specific verb and resource ('Rend le vocabulaire exact des filtres du catalogue') and enumerates exactly what is returned: 41 modules, 3 spot sub-types, 4 disciplines, each with slug, French label, and synonyms. It is clearly distinguishable from ridemypark_search_spots, which is named as the consumer of this taxonomy.

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 states a concrete trigger: use it when a search must be filtered precisely and the person's wording may not be a catalogue slug, with examples ('un bol' → 'bowls', 'escaliers' → 'stairs'). It also points to the ridemypark_search_spots discipline filter as the downstream consumer. There is no explicit when-not condition, which keeps it just below the top band.

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