Skip to main content
Glama

Outil.io

Sync section

sync_section
Destructive

SYNCHRONISER UNE SECTION SUR TOUT LE SITE (en-tête, menu, pied de page, bandeau). Fait de la section {pageId,sectionId} un composant synchronisé puis, avec linkSimilar (par défaut), remplace par lui la section la plus semblable de chaque autre page (score ≥ minScore) : place et ancre gardées, révision archivée. Ensuite, modifier cette section sur UNE page suffit : les autres pages la reçoivent. À faire avant d’harmoniser en-têtes/pieds de page d’un site cloné, plutôt que de modifier chaque page. publish:true recopie aussi sur les pages déjà publiées.

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": {
      "pageId": "<pageId>",
      "sectionId": "<sectionId>",
      "name": "<name>"
    },
    "name": "sync_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pageIdYes
publishNo
minScoreNo
sectionIdYes
linkSimilarNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true; the description goes further by disclosing exactly what is destroyed (the most similar section on every other page is replaced), what is preserved (position and anchor), that a revision is archived, that matching is gated by a score threshold (minScore), and that publish:true also propagates to already-published pages. This is the kind of mutation-scope and recoverability detail an agent needs before calling a destructive tool.

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 a capitalized action statement, then mechanism, then the practical payoff ('modify on ONE page and the others receive it'), then the when-to-use advice. Dense but efficient; the all-caps opening and the long final clause cost some readability, but no sentence is filler.

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?

For a destructive 6-parameter mutation with no output schema, the description covers mechanism, preservation guarantees, archival, thresholding and publish propagation. Remaining gaps are the undocumented 'name' parameter and no indication of what happens when no page exceeds minScore or how many pages were changed.

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 description coverage is 0%, so the description must carry parameter meaning, and it explains pageId/sectionId as the target pair, linkSimilar as the default-on matching behavior, minScore as the similarity floor, and publish as the re-copy to published pages. The required 'name' parameter is never mentioned anywhere, leaving one real gap.

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?

Starts with a specific verb+resource+scope ('SYNCHRONISER UNE SECTION SUR TOUT LE SITE') and then explains the mechanism: the section becomes a synced component and, with linkSimilar, replaces the most similar section on every other page. That is clearly distinct from siblings like copy_template_section or insert_html_section, which the agent can rule out without opening their schemas.

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 routes usage: do this before harmonizing headers/footers on a cloned site, rather than editing each page individually. That is a real when-to-use plus a named alternative approach. It stops short of stating when NOT to sync (e.g., pages with no sufficiently similar section), so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.