Skip to main content
Glama

Save brand voice

brand_set_voice
Idempotent

Saves the brand voice notes (how this business writes: tone, words to use or avoid). Replaces the previous voice text entirely, so read brand_get first and include anything worth keeping. Uses no quota and sends nothing. Reversible by saving the old text again. Only save what the person dictated or approved. Requires API key scope: draft.

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

Input Schema

NameRequiredDescriptionDefault
voiceYesThe full voice notes to save, in plain sentences. Replaces the current text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that it replaces the previous voice text entirely, uses no quota, sends nothing, is reversible by saving old text again, and requires API key scope draft. These are relevant behavioral details not captured by the structured annotations.

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?

The description is front-loaded and appropriately sized for a simple single-parameter mutation. Every sentence adds operational or safety context without unnecessary detail.

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 simple mutation with one parameter and no output schema, it covers replacement behavior, reversibility, quota impact, and authorization scope. The only minor gap is that it does not describe the response, but no output schema exists and the operation is simple enough that this is not a major omission.

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 schema already documents the single voice parameter at full coverage. The description adds useful meaning about what the text should contain, such as tone and words to use or avoid, and reinforces that it replaces the current text.

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?

The description states a specific verb and resource: saving brand voice notes. It also clarifies what those notes contain and distinguishes this operation from brand_get by telling the agent to read first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit usage guidance: read brand_get first, include anything worth keeping, and only save what the person dictated or approved. This covers when to use it and the key workflow prerequisite.

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