Skip to main content
Glama

Fiche d'un dépôt

parc_depot
Read-onlyIdempotent

Retrieve a repository's read-only health snapshot: last commit, workflow status, open PRs, alerts, CodeQL, ruleset, site/production state, tech stack, and socle usage.

Instructions

Tout ce que le relevé sait d'un dépôt : dernier commit, workflows et leur dernier état, PR ouvertes, alertes, CodeQL, ruleset, site et production, pile technique, usage du socle.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nom": "<nom>"
    },
    "name": "parc_depot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom du dépôt, par exemple mister-cim10.

Output Schema

NameRequiredDescriptionDefault
depotYesLa fiche du relevé, workflows résumés.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and idempotency need no restating. The description adds useful scope ('tout ce que le relevé sait') and lists the data sections returned, but says nothing about freshness, latency, or behavior when a repo name is unknown/inaccessible.

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 front-loaded sentence with no filler; the section enumeration is dense but informative rather than redundant. Slightly long, but every item earns its place by signalling what comes back.

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-value detail needn't be explained, and the description still previews the covered domains. Combined with annotations covering the safety profile and a fully documented single parameter, the definition is essentially complete for an agent to call it correctly.

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?

Only one parameter, with 100% schema description coverage including an example ('mister-cim10'), so the schema fully carries the semantics. The description does not need to add parameter detail, and the baseline of 4 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 states it returns the full record for a single repository ('Fiche d'un dépôt / Tout ce que le relevé sait d'un dépôt') and enumerates the sections: last commit, workflows, open PRs, alerts, CodeQL, ruleset, site, tech stack. This is specific enough to distinguish it from parc_depots (list) and parc_prs (PRs only), though the 'fiche' framing implies rather than states the verb.

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?

No explicit when-to-use or when-not guidance vs. siblings. The single-repo scope is implied by 'd'un dépôt' and by the requirement of a 'nom', and the enumeration suggests it is the all-in-one detail view rather than a targeted query, but the agent must infer that parc_prs/parc_alertes exist for narrower queries.

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