Skip to main content
Glama

RideMyPark

Synthèse d'une zone RideMyPark

ridemypark_get_geo_area
Read-onlyIdempotent

Rend la synthèse publique d'une zone géographique (pays, région ou ville) : combien de spots, leur répartition par sous-type et par module, quelques fiches représentatives, et le texte de présentation affiché sur la page de zone du site.

Sert à répondre à « qu'est-ce qu'il y a à rouler à Bordeaux ? » par une vue d'ensemble, avant d'entrer dans le détail spot par spot.

Paramètres :

  • country (string, obligatoire) : slug du pays (« france »).

  • region (string) : slug de la région, pour une zone régionale.

  • city (string) : slug de la ville, pour une zone urbaine. Exige region.

  • locale ('fr' | 'en') : langue de la prose rendue, défaut fr.

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

Rend : le libellé de la zone, le nombre de fiches, des agrégats (sous-types, modules les plus fréquents), des fiches vitrines avec leur slug, et la prose éditoriale quand elle existe.

Limites connues des données :

  • la prose n'existe que sur les zones travaillées éditorialement ; ailleurs, seuls les agrégats sont rendus ;

  • une fiche non géocodée n'entre dans aucune zone, donc les compteurs sont un plancher, pas un total ;

  • les slugs viennent de la normalisation géo de l'API et se lisent dans ridemypark_browse_geography.

Erreurs :

  • un slug inconnu ne lève PAS d'erreur : la synthèse revient sans fiche. Vérifier les slugs dans ridemypark_browse_geography ;

  • city fourni sans region : l'outil refuse, car l'API lirait alors le pays entier sans le dire.

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": {
      "country": "<country>"
    },
    "name": "ridemypark_get_geo_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoSlug de la ville, pour une zone urbaine.
localeNoLangue de la synthèse rédigée (fr par défaut).fr
regionNoSlug de la région, pour une zone régionale.
countryYesSlug du pays de la zone (« france »).
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.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavior the annotations cannot express: prose only exists on editorially curated areas, non-geocoded spots fall outside every area so counts are a floor rather than a total, and city without region is actively refused because the API would silently widen to the whole country. The unknown-slug behavior (no error, empty synthesis) is exactly the kind of silent-failure disclosure an agent needs.

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?

Front-loaded purpose followed by clearly labeled Paramètres / Rend / Limites / Erreurs blocks; every block earns its place given there is no output schema. Slightly long, and a few parameter lines restate the schema descriptions verbatim, which is minor redundancy.

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 carries the return-value burden itself and does so: area label, record count, aggregates, showcase records with slugs, and optional prose. Combined with the documented data limitations and the explicit error semantics, an agent has everything needed to call it and interpret a thin or empty result 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 coverage is 100%, so the baseline is 3, but the description adds a real cross-parameter rule the schema cannot encode: city requires region, and why. It also clarifies that locale governs the language of the rendered prose rather than of keys, and that country is mandatory with a concrete slug example.

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 opening sentence states a specific verb and resource ("Rend la synthèse publique d'une zone géographique") and enumerates exactly what the synthesis contains: spot count, breakdown by subtype and module, sample records, and editorial prose. The second sentence contrasts it with per-spot detail, so an agent can tell it apart from ridemypark_get_spot or ridemypark_search_spots without opening a schema.

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 a concrete when-to-use framing ("qu'est-ce qu'il y a à rouler à Bordeaux ?" as an overview before drilling into spots) and explicitly routes slug validation to ridemypark_browse_geography. It does not name search_spots directly as the alternative for detailed per-spot queries, leaving that inference to the reader, which keeps it short of a full 5.

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