Skip to main content
Glama

RideMyPark

Détails d'un spot RideMyPark

ridemypark_get_spot
Read-onlyIdempotent

Rend la fiche complète d'un spot RideMyPark : où il est, ses modules, sa note, ses horaires, sa photo et le lien vers sa page publique.

Paramètres :

  • slug (string) : identifiant lisible du spot, tel que rendu par ridemypark_search_spots (« place-louis-pradel-spot »).

  • id (number) : identifiant numérique, à défaut de slug.

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

Rend : titre, type (street / skatepark / pumptrack), adresse et ville, coordonnées, couvert ou extérieur, liste des modules, note sur 5 AVEC son nombre d'avis, horaires d'ouverture avec fuseau quand ils sont saisis, photo, galerie, réseaux sociaux, lien de la fiche.

À savoir sur les données :

  • la note est absente sur la plupart des fiches ; l'outil dit « pas encore notée » plutôt que de rendre 0 ;

  • quand elle existe, elle repose presque toujours sur UN seul avis — le compte est rendu avec la note, ne la présente pas comme un consensus ;

  • les horaires ne sont saisis que sur les spots gérés (skateparks indoor surtout) ; un spot en accès libre n'en a pas ;

  • une fiche sans photo ne rend aucune URL, jamais l'image bouchon du site ;

  • un spot FERMÉ (moderation_status « closed », plus accessible) ou ARCHIVÉ (« archived », n'existe plus) reste lisible par son slug ou son id : la réponse le dit en tête. La recherche ne rend jamais ces spots.

Erreurs :

  • « Aucun spot … » quand le slug n'existe pas : le reprendre d'un résultat de ridemypark_search_spots.

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_get_spot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoIdentifiant numérique du spot, à défaut de slug.
slugNoIdentifiant lisible du spot, tel que rendu par ridemypark_search_spots : « place-louis-pradel-spot ».
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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description goes well beyond them with response-level behavior: an unrated spot says "pas encore notée" rather than 0, closed/archived spots are readable and flagged at the top of the response, and a photo-less sheet returns no URL rather than the site placeholder. The one gap is that all three parameters are optional and the description never says what happens if neither slug nor id is 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 definition is front-loaded with the purpose, then cleanly sectioned into parameters, returns, data caveats and errors, so an agent can scan it. It runs long, and the parameter block largely restates schema fields that are already fully documented. The caveat bullets are dense but each carries decision-relevant information (no fake zero ratings, single-review ratings, no placeholder image).

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?

With no output schema, the description correctly compensates by enumerating the returned fields and warning about rating/hours/photo edge cases. It also documents the error surface ("Aucun spot …") and how to recover by reusing a search result. The remaining hole is that the tool accepts zero required parameters and the description never specifies the outcome of calling it with neither slug nor id.

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 100%, so the baseline is 3 and the schema already documents all three parameters. The description nonetheless adds a resolution hierarchy the schema does not express (slug first, id as fallback) and reinforces the slug example format. It does not explain the fallback/error behavior for response_format beyond the enum default already in the schema.

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 opens with a specific verb and resource ("Rend la fiche complète d'un spot RideMyPark") and enumerates what the sheet contains (location, modules, rating, hours, photo, public link). It also distinguishes this tool from ridemypark_search_spots by stating that search never returns closed or archived spots while this tool does, so an agent can route between the two 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where the slug comes from ("tel que rendu par ridemypark_search_spots") and establishes a preference order between slug and id ("à défaut de slug"). The note that closed/archived spots remain readable here but never appear in search is an implicit when-to-use signal. There is no explicit exclusion or when-not-to-use statement, which keeps it short of a 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