Skip to main content
Glama

Save brand kit

save_brand
Idempotent

Make a brand kit or change one. Look at the brand's public website first for its colours, fonts, logo, voice and a plain call to action; don't invent claims. Only the fields you pass change. A logo_url is copied into the studio. The studio shows the kit straight away. Free.

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": "save_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNoDefault call to action, e.g. Try Pro free
nameNoRequired for a new kit
voiceNo
colorsNoA new kit needs all five. The accent also colours the call-to-action button.
websiteNoAs it should read on the end card, e.g. dividendmapper.com
brand_idNoThe kit to update. Omit to update the kit with this name, or make a new one.
headlineNoDefault headline
logo_urlNoPublic PNG, WebP or SVG with transparency. Copied into the studio, so it keeps working if the link changes.
body_fontNo
add_assetsNoProduct photos or app screenshots to copy into the kit. Never take them from behind a login.
remove_logoNo
small_printNoDefault small print, e.g. Capital at risk.
heading_fontNo
visual_styleNo
remove_asset_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses patch-style updates through "Only the fields you pass change," immediate studio visibility, public-source grounding, and zero cost. The logo-copying statement largely repeats the schema, and explicit logo or asset removal behavior is not explained.

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?

The description is compact and front-loads the create/update purpose, followed by sourcing rules and operational effects. Each short sentence contributes actionable information without unnecessary elaboration.

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?

For a 15-parameter nested create/update tool with no output schema, it covers the central workflow, partial-update behavior, immediacy, and cost while the schema supplies most invocation details. It would be more complete with explicit create-versus-update selection guidance and clarification of asset removal or the returned result.

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?

With 60% schema coverage, the description adds useful cross-parameter semantics: omitted fields remain unchanged, and website research should ground colours, fonts, logo, voice, and call to action. It does not further explain visual_style or the removal fields, and the logo_url detail adds little beyond that parameter's schema description.

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 verbs "Make" and "change" paired with "brand kit" clearly establish both creation and update of a specific resource. It does not explicitly differentiate itself from siblings such as get_brand or list_brands.

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?

The instruction to inspect the brand's public website first and avoid invented claims provides a concrete prerequisite and content-sourcing policy. However, there is no explicit when-not guidance or routing to a sibling for discovering or inspecting existing kits.

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