Skip to main content
Glama

Add a logo, font or picture

add_brand_file
Destructive

The short way to add a file: a logo (the Primary), a font (role display or body) or a picture, from a public https url or its bytes. add_logo, add_font and add_pictures do the same with more say. For files on the agent's own machine, get_upload_link gives an address to send them to from your shell, so nothing big passes through your messages.

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": {
      "kind": "<kind>"
    },
    "name": "add_brand_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https address of the file. Marsell fetches it itself (public addresses only, up to 8 MB).
kindYeslogo (the Primary), font (role display or body) or picture.
lookNoWith character: which of its looks this is ("3D", "drawn flat"), by its name in add_characters.
roleNoFor a font.
placeNoThe business's own place it shows, by its name in add_places; the picture joins that place.
familyNoFor a font: its family name.
captionNoFor a picture: what it shows.
filenameNoIts file name with its extension, when you have one.
characterNoThe business's own character it shows (a mascot, a host), by its name in add_characters; the picture joins that character.
data_base64NoOr the file's bytes, base64 (as large as one MCP message carries, about 4 MB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Adds real context beyond the annotations: source must be a public https address that Marsell fetches itself, 8 MB cap for URL fetching, ~4 MB for base64 bytes, and the note that large payloads need not pass through messages. However destructiveHint=true is never explained — the description does not say whether adding a logo replaces the existing Primary or what happens on a name collision, which is the most consequential behavior for a mutating tool.

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 sentences, front-loaded with the core action and the kind enumeration, then the alternatives and the local-file escape hatch. No filler and no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Transport, size limits and sibling routing are well covered for a ten-parameter tool with no output schema. But for a destructive, open-world mutation it omits overwrite/conflict semantics and any hint of what is returned, leaving an agent unsure of the effect on existing brand assets.

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%, so the schema already documents all ten parameters, giving a baseline of 3. The description adds a little by framing url and data_base64 as alternative sources and tying kind to role, but it contributes no format or constraint detail the schema lacks.

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 ('add a file') and enumerates the three file kinds with their domain meaning (logo = the Primary, font with display/body role, picture). It explicitly positions itself against add_logo, add_font and add_pictures, so an agent can pick it without opening a schema.

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?

Names the three sibling alternatives and characterizes the tradeoff ('do the same with more say'), and routes local-machine files to get_upload_link with a rationale. What is missing is an explicit trigger for choosing this over the verbose siblings beyond the loose phrase 'the short way'.

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.