Skip to main content
Glama

RideMyPark

Article complet du blog

ridemypark_get_blog_article
Read-onlyIdempotent

Rend un article de blog RideMyPark en entier : titre, chapô, corps, auteur, date de publication, étiquettes et lien public.

Paramètres :

  • slug (string, obligatoire, 1 à 200 caractères) : identifiant lisible de l'article.

  • locale ('fr' | 'en') : langue demandée, défaut fr.

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

Rend : titre, chapô, corps HTML de l'article, auteur, catégorie, étiquettes, date de publication ISO, image de couverture, langue d'origine (content_lang), langue servie (served_lang) et lien public.

Limites connues des données :

  • le corps peut être long ; la réponse est plafonnée en taille et le dit quand elle a été tronquée ;

  • un article sans traduction dans la langue demandée est rendu dans sa langue d'origine (served_lang le dit) ;

  • un brouillon n'est jamais rendu, même avec le bon slug.

Erreurs :

  • « Aucun article … » quand le slug n'existe pas ou n'est pas publié : le reprendre d'un résultat de recherche d'articles.

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": {
      "slug": "<slug>"
    },
    "name": "ridemypark_get_blog_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant lisible de l'article, tel que rendu par la recherche d'articles.
localeNoLangue demandée, défaut fr.fr
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, openWorld), the description discloses real behavioral traits: body responses are size-capped and flagged when truncated, articles without a translation fall back to their original language via served_lang, and drafts are never returned. These are exactly the surprises an agent needs to anticipate.

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 description is front-loaded with one strong purpose sentence, then breaks into labelled sections (Paramètres, Rend, Limites, Erreurs) that make scanning easy. The parameter block partially duplicates the schema, which is the only wasted content.

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?

There is no output schema, so the explicit return-field list is essential and provided; the limits and error sections cover truncation, language fallback and unpublished slugs. For a 3-parameter read tool this leaves no operational question open.

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?

Schema coverage is 100%, so parameters are already documented in the input schema. The description restates slug, locale and response_format with much the same wording the schema uses, adding only the error hint about where the slug comes from. Baseline 3 is appropriate when the schema does the heavy lifting.

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 un article de blog ... en entier" names a specific verb and resource, and immediately enumerates the returned parts (titre, chapô, corps, auteur, date, étiquettes, lien public). The error section ties the slug to "un résultat de recherche d'articles", which implicitly separates this tool from ridemypark_search_blog.

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?

The error guidance ("reprendre d'un résultat de recherche d'articles") tells the agent to obtain the slug from the blog search tool rather than invent one. It does not explicitly state when to prefer search versus full retrieval, but the context is clear enough for correct selection.

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