Skip to main content
Glama

save_business_brand

Idempotent

Save the complete brand book for the approved business. Read the current brand and confirm changes with the owner before saving.

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

Input Schema

NameRequiredDescriptionDefault
brandYes

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 already declare readOnly=false, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds two non-annotation traits: this writes the *complete* brand book (implying a full replacement rather than a merge) and requires an owner confirmation step before the write. It omits what happens to fields left out or how validation failures surface.

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 short sentences, front-loaded with the action and immediately followed by the prerequisite workflow. No filler, no restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a deeply nested payload and no output schema, the description covers the workflow but not the outcome: no mention of replacement semantics for existing brand assets, permission requirements, or error behavior. Adequate to invoke the tool, but not complete against the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single nested parameter with 0% schema description coverage, so the schema itself only documents the required keys and enums (fonts, booleans) and leaves colors as bare hex strings. The description contributes the notion that the whole object must be supplied, but says nothing about nested structure, allowed font values, or the hex format constraint.

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?

States a specific verb and resource ("Save the complete brand book") plus a scope qualifier ("for the approved business"), which cleanly distinguishes it from the read-side sibling get_business_brand. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

Gives a clear ordering rule: read the current brand and confirm changes with the owner before saving. That is actionable pre-call guidance, but there are no when-not conditions (e.g., what to do for a brand-new business with no existing brand, or which siblings handle location/service branding instead).

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