Skip to main content
Glama

Renovate en attente

parc_renovate
Read-onlyIdempotent

Check Renovate's Dependency Dashboard for pending updates and unresolved packages before manually updating a library, ensuring no existing PR already covers it.

Instructions

Ce que Renovate attend dans chaque dépôt, lu dans son « Dependency Dashboard » : les mises à jour en attente (majeures signalées) et les paquets qu'il ne sait pas résoudre. Avant de monter une librairie à la main, vérifier ici qu'une PR Renovate ne la couvre pas.

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": "parc_renovate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
depotsYes
genereYesDate du relevé qui fonde la réponse (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and network behavior are covered structurally. The description's real added value is disclosing the data source (Dependency Dashboard) and the notion of 'majeures signalées', but it says nothing about scope cost (one dashboard per dépôt) or freshness of the data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the first defines the content, the second the pre-check use case. Purpose is front-loaded and each clause earns its place.

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?

An output schema exists, so return structure needn't be described; the description correctly focuses on semantics (what 'pending', 'major', 'unresolvable' mean). The only gap is that the openWorld / per-repository scan nature and any throttling or latency are not mentioned.

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?

The tool takes zero parameters, so the baseline is 4. The description does not mislead about inputs and correctly frames the tool as a global, no-argument scan across repositories.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (le « Dependency Dashboard » de Renovate) and enumerates exactly what it returns: mises à jour en attente, majeures signalées, paquets non résolubles. It is clearly a read-only inspection tool, though it doesn't explicitly contrast itself with nearby siblings like parc_librairies_en_retard or parc_prs.

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?

Gives an explicit trigger: 'Avant de monter une librairie à la main, vérifier ici qu'une PR Renovate ne la couvre pas.' That is a concrete use case and implicitly an exclusion (don't hand-bump a lib without checking here), but no sibling is named as an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.