Skip to main content
Glama

RideMyPark

Compteurs publics RideMyPark

ridemypark_get_platform_stats
Read-onlyIdempotent

Rend les compteurs vitrine publics de RideMyPark : nombre de spots référencés, nombre de riders inscrits, nombre de villes couvertes.

Sert à répondre à « c'est gros, RideMyPark ? » avec les chiffres affichés sur la page d'accueil, plutôt qu'avec une estimation.

Paramètres :

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

Rend : data.spots (spots référencés), data.riders (riders inscrits) et data.cities (villes couvertes). Aucune date de calcul n'est rendue.

Limites connues des données :

  • ce sont les compteurs VITRINE, mis en cache côté API : ils peuvent avoir quelques heures de retard ;

  • le compte de spots exclut les fiches fermées et archivées, contrairement à un total brut de base ;

  • aucun chiffre de fréquentation, de trafic ni de revenu n'est exposé ici.

Erreurs :

  • Service momentanément saturé : réessayer dans un instant.

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

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.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses that the figures are API-side cached and may lag by hours, that spot counts exclude closed and archived listings unlike a raw DB total, that no traffic or revenue data exists here, and that a saturated service should be retried. These are exactly the behavioral caveats an agent needs to avoid misreporting numbers.

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?

Purpose is front-loaded, then cleanly sectioned into parameters, return shape, data limits and errors, which makes it skimmable. It is slightly longer than necessary because the parameter bullet and the 'Rend' line partly duplicate the schema's enum default.

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-shape burden and does so by naming data.spots, data.riders and data.cities plus the absence of a computation date. Caching staleness, count exclusion rules and the retry error are all covered, leaving nothing an agent needs missing.

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 optional parameter with 100% schema coverage, so the schema already explains 'markdown' vs 'json' and the default. The description merely restates the same enum and default, adding no new meaning; baseline 3 applies.

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 the exact resource ('compteurs vitrine publics de RideMyPark') and enumerates the three metrics returned (spots, riders, cities). No sibling in the catalog returns statistics, so an agent can immediately tell this is the only source for platform-level totals.

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 usage scenario ('répondre à « c'est gros, RideMyPark ? » avec les chiffres affichés sur la page d'accueil, plutôt qu'avec une estimation') and explicitly rules out estimating. It does not name a competing tool or state when not to call it, which keeps it just 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