Skip to main content
Glama

Outil.io

List synced components

list_synced_components
Read-only

Composants synchronisés du site (en-têtes, pieds de page, bandeaux, groupes) : nom, type et pages qui les utilisent. Modifier UNE instance (apply_page_changes, apply_site_changes, éditeur) la recopie sur toutes ces pages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavioral context the annotations cannot convey: that editing ONE instance of a synced component propagates to every page that uses it, which is critical context for the agent when deciding whether a follow-up mutation is safe. It also discloses the shape of the result (name, type, using pages) despite there being no output schema.

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?

Two dense sentences, front-loaded with the resource and its contents, followed by the propagation warning. The parenthetical enumerations are informative rather than filler, though the second sentence packs three alternative tool names into one clause, slightly reducing readability.

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 zero-parameter, read-only list tool with no output schema, the description supplies enough: what is listed, which fields come back, and the cross-page side effect of modifying a synced instance. The main residual gap is pagination or result-size expectations, which the description never addresses.

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 takes zero parameters, so the baseline is 4. The description correctly implies no filtering input is needed, and instead spends its words on what the call returns.

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 names the exact resource (synced components of the site) and enumerates the component kinds covered (headers, footers, banners, groups) plus the fields returned (name, type, pages using them). It also implicitly separates this read tool from the mutating siblings it names (apply_page_changes, apply_site_changes). The only weakness is the absence of an explicit verb form and the French/English mismatch with the tool name.

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?

Usage is implied rather than stated: the agent can infer this is the tool to consult for an inventory of synced components before modifying one. The second sentence steers the agent toward apply_page_changes / apply_site_changes / the editor when the intent is mutation, which is genuine routing guidance, but there is no explicit 'use this when' or exclusion statement.

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.