Skip to main content
Glama

Get Brand Tool

get_brand
Read-only

Get a saved brand kit: colors, fonts, logo URLs, notes, and the exact Tailwind classes it adds (bg-brand-primary, font-heading and so on). Call this before rendering for a brand.

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

Input Schema

NameRequiredDescriptionDefault
slugYesBrand slug from list_brands.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is to add context — and it does, disclosing that the kit resolves to concrete Tailwind classes (bg-brand-primary, font-heading) and that the result feeds rendering. It says nothing about behavior for an unknown slug (error vs empty), which is the main remaining unknown for a lookup by key.

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 first declares what is returned, the second states when to call it. Front-loaded, zero filler, and the parenthetical examples earn their space by making the Tailwind output concrete.

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, the description carries the return-value burden and discharges it by listing the kit contents. For a one-parameter read tool with readOnlyHint already declared, nothing an agent needs in order to call it correctly is missing.

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 parameter with 100% schema description coverage, and the schema already explains that slug comes from list_brands. The description adds no format, casing, or resolution detail beyond that, so baseline 3 applies.

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?

"Get a saved brand kit" pairs a specific verb with a specific resource and then enumerates the payload (colors, fonts, logo URLs, notes, Tailwind classes), so the agent knows exactly what comes back. It never explicitly contrasts itself with list_brands, so sibling differentiation is implied by the singular "brand kit" 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?

"Call this before rendering for a brand" gives a concrete trigger and a downstream dependency, which is genuinely actionable sequencing guidance. It does not name when to skip or which sibling to use instead (e.g., list_brands for discovery), so it stops short of full when/when-not coverage.

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