Skip to main content
Glama

Logo and colours

set_branding

Sets the venue logo from a public https link to a PNG, JPG or WebP file (up to 300 KB), and/or its three colours as #rrggbb: hot (buttons, highlights), fresh (light accent), sun (yellow accent). Colours need the Plus or Pro plan (included in the trial). Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>"
    },
    "name": "set_branding"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotNo
sunNo
freshNo
addressYesThe venue’s address name, the "name" in name.bookare.app.
logo_urlNo
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, open-world), so the description's job is to add operational context and it does: file type/size constraints, plan entitlement, and the single-venue scope tied to address plus access key. It stops short of saying what happens on a rejected image or whether the prior logo is replaced, but the added context is substantive.

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?

Three sentences, front-loaded with what is being set, then the constraints, then the plan rule and scoping. Dense but every clause carries information; only the trial parenthetical is arguably marginal.

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 6-parameter mutation with no output schema and thin schema documentation, the description supplies the format limits, the colour semantics, the plan requirement and the venue targeting needed to call it correctly. What is missing is failure behaviour and whether setting is a full replace, which keeps it below 5.

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 only 33%, so the description must carry the load and largely does: logo_url gets accepted formats (PNG/JPG/WebP), a public https requirement and a 300 KB cap; hot/fresh/sun get #rrggbb format plus the UI meaning of each (buttons/highlights, light accent, yellow accent). It adds nothing about whether colour params are optional or what an omitted colour does, which is the remaining gap.

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 and two concrete resources: sets the venue logo (from a URL) and/or its three brand colours, with the three colour slots named. An agent can tell this apart from set_cover_photo because the description names the logo and brand palette explicitly, though it never names a sibling to route away to.

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 'and/or' phrasing makes clear the two operations can be done independently or together, and the plan gating (Plus/Pro, included in trial) is a real usage precondition. There is no explicit statement of when to prefer this over set_cover_photo or how to clear/remove existing branding, so guidance is implied rather than complete.

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