Skip to main content
Glama

Get organization brand kit

get_brand_kit
Read-onlyIdempotent

Read the brand kit of an organization: brand name, colors by shape type (step, decision, actor, system, data, start, end, screen), canvas font, whether a logo is set, and the naming and tone guide the AI follows when it builds flows.

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

Input Schema

NameRequiredDescriptionDefault
org_idYesOrganization id from list_organizations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, disclosing that the response includes per-shape-type colors, canvas font, a logo flag, and the naming/tone guide used by the AI. It stops short of noting defaults or what an unset brand kit returns, but adds real value beyond the annotations.

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?

One front-loaded sentence with a colon-introduced field list; the parenthetical shape-type enumeration is long but each token is meaningful content the agent would otherwise lack.

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?

No output schema exists, so the description usefully stands in for it by naming the returned fields. For a one-parameter read tool with full annotation coverage, that is nearly complete — only edge cases like a missing/unset brand kit are unaddressed.

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 coverage is 100% and the single org_id parameter is already documented in the schema as coming from list_organizations, so the description adds nothing new about parameters. Baseline 3 applies.

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?

States a specific verb and resource ("Read the brand kit of an organization") and then enumerates exactly what the kit contains, so an agent can tell it apart from set_brand_kit and the other get_* organization tools without opening any schema.

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 read/read-only framing implies when to use it versus the mutating sibling set_brand_kit, but the description never names that alternative or states any precondition beyond the parameter. Usage is implied rather than instructed.

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