mister-parc-mcp

Pull requests ouvertes

parc_prs

Read-onlyIdempotent

List open pull requests across all repositories in the account, oldest first, with repo, branch, author, draft status, and CI state; optionally include bot PRs. Read-only; does not merge.

Instructions

Les pull requests ouvertes sur tout le compte, les plus anciennes d'abord : dépôt, numéro, titre, branche, auteur, brouillon ou non, et l'état de leur CI.

Dans ce parc, une PR ne se fusionne que sur la décision du propriétaire : cet outil les liste, il ne fusionne rien.

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

Input Schema

Name	Required	Description	Default
`robots`	No	Garder aussi les PR ouvertes par un robot (Renovate…).

Output Schema

Name	Required	Description	Default
`prs`	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.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 adds real context beyond that: results span the entire account, are sorted oldest-first, and each row carries repo, number, title, branch, author, draft status and CI state. The explicit 'it does not merge anything' also preempts a wrong assumption about a PR tool in a repo where merges are owner-gated.

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?

Two sentences, front-loaded with what is listed and in what order, followed by the read-only clarification. The field enumeration is somewhat long but each field is informative; there is little waste.

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 the description need not explain return shape, and annotations cover the read-only/idempotent profile. What remains unaddressed is how this relates to parc_renovate and whether results are paginated — minor gaps for a single-parameter listing tool.

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 single 'robots' parameter is fully documented in the schema with its default. The description does not mention bot filtering at all, so it adds nothing to parameter meaning; baseline 3 applies.

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 gives a specific verb and resource ('Les pull requests ouvertes sur tout le compte'), plus scope (whole account), ordering (oldest first) and the fields returned. It is clear what the tool does, but it never names or distinguishes itself from siblings such as parc_renovate, which likely surfaces overlapping bot-authored PRs.

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 second sentence usefully sets a boundary ('cet outil les liste, il ne fusionne rien'), telling the agent this is a listing, not a merge action. However, there is no explicit guidance on when to pick this tool versus parc_renovate or parc_depots; the choice is left to inference.

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