Skip to main content
Glama

Ce que le socle offre

socle_offre
Read-onlyIdempotent

Lists modules by category, CLI tools, reusable workflows, and required peer dependencies for the published version of the shared foundation, so teams can check what it already provides.

Instructions

Ce que la dernière version publiée du socle offre : ses modules rangés par catégorie (composants, crochets React, configs Vite, outillage…), ses outils en ligne de commande, ses workflows réutilisables, et les dépendances pairs qu'il attend des applications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
pairsYesDépendances pairs que le socle attend des apps.
outilsYesOutils en ligne de commande : pwa-doctor…
modulesYesLes modules, par catégorie.
versionYes
workflowsYesWorkflows réutilisables : pwa-ci.yml…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/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 useful scope by saying it reflects only the latest published version and by listing what categories are included, but it does not add further operational caveats such as freshness guarantees or authentication requirements.

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?

The description is a single front-loaded sentence that immediately states the scope: latest published version of the socle's offering. The parenthetical category list is dense but each item adds useful detail, and there is no redundant wording.

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?

With an output schema present, the description does not need to explain return values, and zero parameters keep invocation simple. It gives enough scope for an overview tool, though it could be more complete by explaining how this overview relates to the specific socle_* sibling 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 has zero parameters, so parameter semantics carry little burden. The schema description coverage is 100%, and the baseline for a no-parameter tool is 4.

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?

States specifically that the tool returns what the latest published version of the socle offers, enumerating modules by category, command-line tools, reusable workflows, and peer dependencies. It is clearly an aggregate catalog rather than a detail tool, though it does not explicitly name the sibling detail tools it complements.

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 explicit guidance on when to use this tool versus alternatives such as socle_module, socle_workflow, or socle_doc. An agent can infer that this is an overview tool from the description and sibling names, but the description itself provides no when-to-use or when-not-to-use guidance.

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