mister-parc-mcp

Module du socle

socle_module

Read-onlyIdempotent

Retrieve a module's category, bundled and dependent modules, and repositories that import it directly to check coverage and reuse before duplicating code.

Instructions

Un module du socle : sa catégorie, les modules qu'il emporte avec lui, ceux qui l'emportent, et les dépôts qui l'importent directement.

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

Input Schema

Name	Required	Description	Default
`nom`	Yes	Nom du module, tel que l'importe une app : react/i18n, analytics…

Output Schema

Name	Required	Description
`nom`	Yes
`emporte`	Yes	Modules qu'il emporte, transitivement.
`version`	Yes
`categorie`	Yes
`emporte_par`	Yes
`importe_par`	Yes	Dépôts qui l'importent directement.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds some semantic context by disclosing that the result includes transitive relationships in both directions plus direct importer repos. It still says nothing about behavior on an unknown module name (empty result vs. error) or about the cost of traversing this graph.

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 with the entity front-loaded and no filler. The only inefficiency is that nearly all of its words go to describing the payload rather than the action, which is partially redundant given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup with 100% schema coverage and a dedicated output schema, the description is close to sufficient — the agent knows the entity and the shape of the answer. It is still missing the lookup semantics (exact name match, behavior when the module doesn't exist) and any routing hint to the sibling search 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 'nom' property already carries an example format ('react/i18n, analytics…'). The description adds nothing about the parameter — no matching rules, no exact-vs-prefix semantics — so the baseline 3 for high coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (a socle module) and enumerates the facets returned (category, carried modules, carriers, direct importing repos), so an agent can infer this is a per-module lookup. However, it never states a verb — no 'get'/'retrieve' — and it reads as a data model summary rather than a purpose statement. It also does nothing to separate itself from socle_chercher or socle_offre among the siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says whether to call this with an exact module name versus using socle_chercher for fuzzy lookup, and no mention of the other socle_* tools. Usage is only implied by the single required 'nom' parameter.

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