mister-parc-mcp

Alertes de sécurité

parc_alertes

Read-onlyIdempotent

View open security alerts across your fleet. Get Dependabot vulnerability details (CVE/GHSA) and CodeQL findings, filtered by repository or shown globally.

Instructions

Les alertes ouvertes, dépôt par dépôt : vulnérabilités Dependabot (avec leurs identifiants CVE ou GHSA, et combien touchent la production) et alertes CodeQL (avec la règle en cause). Sans depot, seuls les dépôts qui ont au moins une alerte.

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

Input Schema

Name	Required	Description	Default
`depot`	No	Un seul dépôt ; sinon tous ceux qui ont des alertes.

Output Schema

Name	Required	Description
`depots`	Yes
`genere`	Yes	Date du relevé qui fonde la réponse (ISO 8601).
`lisibles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description goes further by stating that only *open* alerts are returned and by enumerating what each record contains (CVE/GHSA ids, production-affected count, CodeQL rule) and the default filtering when no repository is given — real added context.

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?

A single compact sentence that front-loads what the tool returns and then qualifies the default case. Every clause carries information; only the parenthetical field lists make it slightly dense.

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 an output schema present and one fully documented parameter, the description need not explain return shapes — yet it still outlines the payload contents, which helps the agent anticipate results. Nothing essential for correct invocation is missing; only sibling routing guidance is absent.

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 description coverage is 100% and the `depot` description already says 'un seul dépôt ; sinon tous ceux qui ont des alertes.' The description restates the default scoping behavior, adding only mild emphasis that repos without alerts are excluded. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

The description names a specific resource (open Dependabot and CodeQL alerts) and details the per-repository breakdown plus the key returned fields (CVE/GHSA identifiers, production impact count, offending rule). It is clearly actionable, though it never explicitly contrasts itself with the dependency-adjacent sibling parc_renovate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The only guidance is behavioral scoping: 'Sans `depot`, seuls les dépôts qui ont au moins une alerte.' That tells the agent what omitting the parameter does but says nothing about when to pick this tool over parc_renovate, parc_depots, or parc_a_faire. Usage is implied rather than directed.

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