mister-parc-mcp

Échecs de CI

parc_echecs

Read-onlyIdempotent

Lists failing CI workflows on the default branch, showing the repository, workflow, job, failed step, and run link. An empty list confirms all workflows are green.

Instructions

Les workflows rouges sur la branche par défaut : dépôt, workflow, job et étape en échec, lien du run. Une liste vide veut dire que tout est vert.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

A3.9/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 adds genuine context beyond that: results are scoped to the default branch only, and an empty result is a meaningful positive signal rather than a failure state. It does not discuss freshness, pagination or volume limits, keeping it short of a 5.

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 short clauses, front-loaded with what is returned, followed by the empty-result interpretation. Every sentence carries information and nothing is padded.

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 values need not be re-explained, and the description still supplies the key scope constraint (default branch) and the empty-list semantics. For a zero-parameter read tool this is nearly complete; the only soft gap is the lack of any routing hint versus related parc_* tools.

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 schema is closed (additionalProperties: false) and fully described, and the description correctly adds no parameter discussion, which is appropriate.

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 the specific resource (red workflows on the default branch) and even enumerates what each entry contains: repository, workflow, job, failing step, run link. It is clear what the tool returns, though it does not explicitly distinguish itself from near-neighbours such as parc_alertes or 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?

Usage is implied rather than stated: an agent can infer it should call this to check CI health, and 'une liste vide veut dire que tout est vert' gives a useful interpretation rule. However, there is no explicit when-to-use/when-not guidance and no named alternative among the many parc_* siblings.

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