Skip to main content
Glama
Sign In
mcp-pilotage

mcp-pilotage

by fmenguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apercu_ecosysteme

Get a compact Markdown overview of every project grouped by family, including role, stack, current branch, and last git activity, to understand the workspace at session start.

Instructions

Briefing de démarrage à froid : une synthèse markdown compacte de tout l'écosystème de François, projets regroupés par famille, avec pour chacun son rôle, sa pile, sa branche courante et sa dernière activité git. C'est l'outil à appeler au tout début d'une session quand tu arrives dans un dépôt sans contexte et que tu veux comprendre en un seul appel ce que François fabrique, combien de projets il a, lesquels sont vivants et lesquels dorment. Plus dense que lister_projets et déjà mis en forme. Si tu as besoin des données brutes pour les filtrer toi-même, utilise plutôt lister_projets.

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

Input Schema

NameRequiredDescriptionDefault
rafraichirNoForcer un nouveau scan du disque en ignorant le cache interne.
inclure_gitNoInterroger git pour chaque dépôt (branche, date du dernier commit, niveau d'activité). Mettre à false rend la réponse quasi instantanée mais sans l'information de fraîcheur.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return format (markdown, pre-formatted), density relative to lister_projets, and the presence of git-derived freshness data. It does not state that this is a read-only operation or that a default call triggers a disk scan — though the schema's rafraichir/inclure_git parameters partially cover the caching and cost trade-off.

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?

Front-loaded with the core purpose, then use case, then the sibling alternative — a logical ordering with no filler paragraphs. It is somewhat verbose with overlapping clauses about understanding what François builds, and one clause restates the timing guidance already given.

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?

No output schema exists, and the description compensates by describing the return shape (compact markdown synthesis, grouped by family with per-project fields) so the agent knows what it will get. For a two-optional-parameter, zero-risk read tool, nothing needed to call it correctly is missing.

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%, so both parameters (rafraichir, inclure_git) are already fully documented in the schema, including the cache bypass and the latency/freshness trade-off. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Names a specific artifact (a compact markdown cold-start briefing) and enumerates its contents — projects grouped by family, each with role, stack, current branch and last git activity. It explicitly contrasts itself with lister_projets, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('au tout début d'une session quand tu arrives dans un dépôt sans contexte') plus the questions it answers (how many projects, which are alive vs dormant). It also names the alternative and the condition for switching: use lister_projets when you need raw data to filter yourself.

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

Deploy Server

Other Tools