Skip to main content
Glama

Gridly — AI copilot for WooCommerce

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 Gridly 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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds substantive context: the write is a scoped save-or-replace of a named preset, deletion happens through the same tool via remove=true, and no store data is touched. It stops short of saying whether a replace is reversible or what happens to prior guidelines when they are omitted.

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 tight sentences: the save/replace semantics and content shape come first, then the scope guarantee and the delete flag. No sentence is filler and the destructive path is placed where an agent will read it.

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 with no output schema and annotations covering the safety profile, the description supplies purpose, content shape, scope, and the delete path. The remaining gap is what a partial re-save does to unspecified fields (merge vs. full replace) and whether any confirmation is returned, which matters for a destructiveHint=true tool.

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 the load — and it does for all three parameters: 'name' as a named style with examples, 'guidelines' as tone/words-to-use-or-avoid/length, and 'remove=true' for deletion. It omits the maxLength bounds (60/2000) and does not clarify whether guidelines is required for a save versus a delete.

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+resource ('Saves (or replaces) a named writing style') and immediately gives concrete shape to the resource: tone, words to use or avoid, typical length, with examples like 'Friendly' or 'Luxury'. The scope clause 'Saved in the user's Gridly account only — nothing in the store changes' cleanly separates it from the store-mutating siblings (update_products, update_order, create_coupon).

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?

The create-or-replace framing plus the explicit 'Set remove=true to delete a preset' covers the two main invocation modes an agent needs. It does not name get_brand_voice as the read alternative or state when to prefer reading over re-saving, so routing to the sibling is left to inference.

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