Skip to main content
Glama

Outil.io

Update brand kit

update_brand_kit
Destructive

Modifier la charte : envoyer seulement les sections/champs à changer (fusion). Exige la version lue (0 si jamais enregistrée). Polices disponibles : Poppins, Montserrat, Inter, Playfair Display, Lora, Roboto, Open Sans, Lato, Raleway, Oswald, Merriweather, DM Sans. Met à jour d’office les pages légales existantes si l’identité de l’entreprise change.

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": {
      "version": "<version>",
      "kit": "<kit>"
    },
    "name": "update_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kitYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description earns credit by explaining the destructive scope: partial merge preserves unspecified fields, and existing legal pages are automatically overwritten when company identity changes. It does not cover permission/auth requirements or how a version conflict surfaces as a response.

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

Conciseness3/5

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

Merge semantics and the version rule are front-loaded and well ordered, but the twelve-item font list is a long block that merely restates the schema enum and consumes a large share of the text without adding decision-relevant information.

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 deeply nested mutation with no output schema, the description covers the essentials: partial-merge semantics, the optimistic-concurrency version, and the automatic legal-page side effect. What remains thin is error/conflict behavior and the fact that nested objects are all optional.

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 description adds meaning beyond the schema by explaining that the 'kit' object is merged rather than replaced, and that 'version' is the previously read version with 0 meaning 'never saved' (the schema only says minimum 0). The 12-font enumeration partly duplicates the schema enum, limiting the gain.

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 opens with a specific verb+resource ('Modifier la charte') and immediately defines the update modality as a merge ('envoyer seulement les sections/champs à changer'), which distinguishes it from a full replace. It doesn't name the sibling get_brand_kit explicitly, though the version-read requirement implies it.

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?

It gives clear usage context: send only the sections/fields to change, and supply the version previously read (0 if never saved), which defines the correct call workflow. It stops short of stating exclusions or what to do when a version is stale beyond the implicit requirement.

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.