mister-parc-mcp

Chercher dans le socle

socle_chercher

Read-onlyIdempotent

Searches the socle for a given term across module names, tools, workflows, and docs to check if a feature already exists before writing new code.

Instructions

Le socle a-t-il déjà ceci ? Cherche le terme, sans égard à la casse, dans les noms des modules, outils et workflows, puis dans les sections de README.md, CONFIG.md et CONTRIBUTING.md. À appeler AVANT d'écrire dans une app ce qui pourrait y être.

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": {
      "terme": "<terme>"
    },
    "name": "socle_chercher"
  }
}

Input Schema

Name	Required	Description	Default
`terme`	Yes	Ce que l'on cherche : prefetch, CSP, Supabase, QR…

Output Schema

Name	Required	Description	Default
`terme`	Yes
`outils`	Yes
`modules`	Yes
`version`	Yes
`sections`	Yes
`workflows`	Yes
`sections_trouvees`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds meaningful behavior beyond that: matching is case-insensitive and happens in a defined order (names first, then documentation sections), which helps the agent interpret results. Return shape isn't described, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the question the tool answers, followed by the search scope and the call-before-writing instruction. No wasted text.

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?

For a single-parameter search tool with annotations and an output schema, the description covers what is searched, how matching works, the search order and when to invoke it. Nothing an agent needs in order 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is self-documenting with examples. The description still adds value by specifying case-insensitive matching and the fields the term is matched against, which goes slightly beyond the schema.

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?

States a specific verb (cherche) and a precise scope: case-insensitive search across module/tool/workflow names then README.md, CONFIG.md and CONTRIBUTING.md sections. This clearly distinguishes it from siblings like socle_module, socle_workflow and socle_doc, which appear to inspect single entities rather than search across all of them.

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

Usage Guidelines4/5

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

Explicitly tells the agent to call it BEFORE writing into an app anything that might already exist in the socle, which is a clear usage trigger. It does not explicitly name an alternative or exclusion (e.g. when to prefer socle_doc or socle_module directly), so it falls short of a 5.

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