Skip to main content
Glama

Get brand kit

get_brand_kit
Read-onlyIdempotent

Get one entry's brand kit, as its owner declared it: logo, pictures, colours, fonts and corners. For showing or building something in the entry's own look.

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": {
      "entry": "<entry>"
    },
    "name": "get_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich entry: its ID or slug, from search or get_entry.
languageNoThe language to answer in, when the entry has it.

Output Schema

NameRequiredDescriptionDefault
urlYes
logoNo
slugYes
fontsNo
colorsNo
cornersNo
entryIdYes
imageryNo
languageYes
revisionYes
displayNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The phrase 'as its owner declared it' usefully signals that values are owner-supplied and may be partial or absent, but the description never says what happens when an entry has no brand kit.

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 compact sentences with no filler; the resource and its contents are front-loaded before the use case. Every clause carries information.

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?

An output schema exists, so return values need no explanation, and this is a simple two-parameter read tool whose definition covers what it fetches and why. The only real gap is the empty/no-brand-kit case, which the agent cannot predict from the text.

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?

Schema description coverage is 100%, so both 'entry' (ID or slug, from search or get_entry) and 'language' are already documented in the schema. The description adds no further meaning about either parameter, 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?

States a specific verb ('Get') and resource ('one entry's brand kit') and enumerates the returned assets: logo, pictures, colours, fonts and corners. That is enough to separate it from get_entry and get_entry_sections, though it never names those siblings explicitly.

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?

'For showing or building something in the entry's own look' implies the intended context, so usage is inferable rather than stated. There is no when-not guidance and no named alternative for the case where a full entry record (get_entry) is what the agent actually needs.

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