Skip to main content
Glama

RideMyPark

Fiche d’une boutique

ridemypark_get_shop
Read-onlyIdempotent

Rend la fiche publique d’une boutique du catalogue RideMyPark.

Paramètres :

  • slug (string, 1 à 200 caractères) ou id (integer > 0) : fournir exactement un identifiant rendu par ridemypark_search_shops.

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

Rend : id, title, slug, url, gallery, links ; description, adresse, lieu, coordonnées, site web, téléphone, horaires, fuseau horaire, photo, état de modération et date de mise à jour quand renseignés. Les horaires sont ceux de la fiche, sans garantie d’ouverture en temps réel.

Limites : les données peuvent être incomplètes ou anciennes. Aucun stock, prix, marque disponible ou achat. Une fiche de spot ou d’événement est refusée.

Erreurs : identifiant absent, ambigu ou inconnu, ou fiche d’un autre univers.

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

Input Schema

NameRequiredDescriptionDefault
idNoIdentifiant numérique de la boutique. Fournir id ou slug.
slugNoSlug de la boutique, rendu par ridemypark_search_shops. Fournir slug ou id.
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?

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), the description discloses substantive behavior: data may be incomplete or stale, no stock/price/brand/availability/purchase information exists, opening hours are as listed and not a real-time guarantee, and the exact error conditions (missing, ambiguous, unknown identifier, or a record from another universe).

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 sentence followed by clearly labeled Paramètres / Rend / Limites / Erreurs blocks, so an agent can scan to the section it needs. The Rend enumeration is somewhat long, but it is justified by the absence of an output schema.

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 and three loosely constrained parameters, the description compensates fully: it lists the returned fields, flags which are conditional, defines the identifier contract, and enumerates failure modes. An agent has everything needed to invoke it and interpret the response 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 schema already documents id, slug and response_format, but the description adds the mutual-exclusivity rule absent from the schema (both properties optional with no oneOf): supply exactly one identifier. It also restates that slug comes from ridemypark_search_shops and that the markdown default applies, which reinforces rather than merely repeats 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?

"Rend la fiche publique d'une boutique du catalogue RideMyPark" states a specific verb (retrieve/return) and resource (a shop's public record), and the Limits section explicitly excludes spot and event records, which separates it from siblings like ridemypark_get_spot and ridemypark_get_event.

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 that the identifier must be one previously returned by ridemypark_search_shops, and it names the exclusion (spot/event records are refused), giving clear preconditions and a negative case. It does not explicitly route the agent to the correct sibling when the record turns out to be a spot or event, so it stops short of full alternative-routing.

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