Skip to main content
Glama

Get brand kit

get_brand
Read-only

A brand kit in full: colours, fonts, logo, website, voice, visual style, default headline, call to action and small print, and the brand's own screenshots and product images with their asset ids. A captured screen lists how many cards, states and flows it has; pass asset_id to get that screen's boxes, crops and states in full.

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_id": "<brand_id>"
    },
    "name": "get_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idNoOne screenshot's id: its card boxes, crop URLs, state captures and flows in full
brand_idYesA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so the safety profile is already covered and the description is free to spend its words on output shape. It does that well: it discloses that a captured screen returns counts of cards, states and flows rather than full detail, and that asset_id is the switch to the complete representation — a progressive-disclosure behavior an agent could not infer from the schema alone.

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?

Two sentences, front-loaded with the payload contents and ending with the asset_id mechanic, with essentially no filler. The first sentence is a long comma-separated inventory, but every item is information an agent needs to know is present.

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?

With no output schema, the description carries the full return-value burden and does so: it names every returned field group plus the nested summary-versus-full behavior for screens. Only minor gaps remain, such as whether the brand_id accepts a name as the schema hints and how large the returned asset list can be.

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 100%, so baseline would be 3. The description goes further by explaining the relationship between the two parameters: a screen arrives summarized and asset_id expands it, which makes the otherwise opaque string id meaningful as a second-stage call. It does not add format or length details beyond the schema.

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?

The description enumerates exactly what the tool hands back — colours, fonts, logo, website, voice, visual style, default headline, CTA, small print, screenshots with asset ids — so the resource is unmistakable. It lacks an explicit verb and never names list_brands (the sibling that produces the brand_id), so differentiation is implied through the schema rather than the description.

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

Usage Guidelines3/5

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

The second sentence gives a concrete conditional: pass asset_id to expand a screen's boxes, crops and states. That is real guidance for the optional parameter, but there is no statement of when to call get_brand versus list_brands or save_brand, and no prerequisites are spelled out.

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