Skip to main content
Glama

Get brand

brand_get
Read-onlyIdempotent

Returns the brand settings: workspace and from name, reply-to, logo, colors, the theme (background, surface, text, button_style, button_shape), the default info_bar, the footer (address, link buttons, disclaimer, social_icons), social profile links, the saved writing voice and the sending domain status. Free and read only. Read this before writing any campaign copy and follow the voice exactly. Requires API key scope: read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "brand_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, closed-world and non-destructive, so the description doesn't need to restate safety. It does add genuinely new context: "Free and read only" (cost implication) and "Requires API key scope: read" (auth prerequisite), plus a mandatory behavioral instruction to follow the returned voice exactly.

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?

Purpose and the enumerated payload are front-loaded, and the operative instructions (read first, follow voice, scope requirement) are short and at the end. The field list is long but each item is a concrete deliverable field, not filler.

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

Completeness5/5

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

With no output schema and no parameters, the description carries the full burden of telling the agent what it gets back, and it does so field by field, including nested groupings like theme and footer. It also covers cost, scope requirement, and how the result should be used.

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 tool takes zero parameters, so the baseline is 4; there is nothing the description could clarify about inputs. The field enumeration instead describes the output shape, which is extra value rather than missing semantics.

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?

"Returns the brand settings" is a specific verb+resource, and the sentence enumerates exactly what comes back (workspace/from name, reply-to, logo, colors, theme fields, info_bar, footer, social links, voice, sending domain status). This is clearly a read-side counterpart to the brand_set_* siblings, so an agent can distinguish it without opening a schema.

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 explicit usage context: "Read this before writing any campaign copy and follow the voice exactly," which tells the agent this is a prerequisite for copy generation. It stops short of naming exclusions or alternatives (e.g., pointing to brand_set_theme for changes), so it is clear but not fully routing.

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