Skip to main content
Glama

Pridly — AI copilot for PrestaShop

Save my brand voice

save_brand_voice
Destructive

Saves (or replaces) a named writing style, for example 'Friendly' or 'Luxury', as plain instructions: tone, words to use or avoid, typical length. Saved in the user's Pridly account only — nothing in the store changes. Set remove=true to delete a preset.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
removeNo
guidelinesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds real value on top by disclosing that an existing preset with the same name is replaced (overwritten), that writes are confined to the user's Pridly account, and that remove=true deletes the preset. It does not mention any confirmation, permission, or failure behavior for the delete path, keeping it short of a 5.

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?

Three short sentences, front-loaded with the core action, then scope, then the delete flag. Nearly every clause earns its place; only the 'nothing in the store changes' phrasing slightly overlaps the account-scope point.

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 3-parameter mutation tool with annotations and no output schema, the description covers action, overwrite semantics, storage scope, and the delete mode. Gaps remain around required fields, length constraints, and what is returned on success or failure.

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 0%, so the description must carry parameter meaning, and it largely does: 'name' is framed as the preset's label with examples, 'guidelines' is described as plain instructions covering tone/words/length, and 'remove=true' is explained as deletion. It omits that name is required and the length limits, so it is not fully compensating.

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 gives a specific verb ('saves/replaces') and resource ('named writing style'), plus concrete examples ('Friendly', 'Luxury') and the content shape (tone, words to use or avoid, length). It implicitly contrasts with the get_brand_voice sibling and with store-mutating tools like apply_product_content, though it never names an alternative explicitly.

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 clearly frames the use case (persisting a reusable writing style in the account) and states the delete path with 'Set remove=true to delete a preset.' The clause 'nothing in the store changes' steers agents away from treating this as a content-application tool, but it does not name the read counterpart or state prerequisites.

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.

Resources