Raziel

tide_branding

Read-only

BRAND THE ENCLAVE FOR THE USER — generate a logo + background and upload them so the Tide login/approval screen is branded. Returns a single ready-to-run command that generates the assets (no image model needed), validates them, uploads both, and saves+signs the IdP settings. Also returns the VERIFIED upload contract (multipart parts, the png/jpg/jpeg/gif/webp allowlist with SVG REJECTED, the 5 MB cap, set-branding = save AND re-sign, IGA-exempt) plus image-model prompts for agents that can generate images. Pass realm/accent/appName to get the command pre-filled. CALL THIS whenever branding, a logo, a background, theming or 'skinning' the enclave or login screen comes up — then RUN the command; do not just describe it.

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

Input Schema

Name	Required	Description
`realm`	No	Realm to brand, e.g. 'myapp'. Fills in the command.
`accent`	No	Hex accent colour without '#', e.g. '2f6f4e'. Default 1f6feb.
`appName`	No	App name. Deterministically varies the mark's geometry so realms look distinct.
`tidecloakUrl`	No	Base URL. Default http://localhost:8080.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed6 schema fields changedAug 17, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / accent

Added value: +{
+  "description": "Hex accent colour without '#', e.g. '2f6f4e'. Default 1f6feb.",
+  "type": "string"
+}

addedInput schema / properties / appName

Added value: +{
+  "description": "App name. Deterministically varies the mark's geometry so realms look distinct.",
+  "type": "string"
+}

addedInput schema / properties / realm

Added value: +{
+  "description": "Realm to brand, e.g. 'myapp'. Fills in the command.",
+  "type": "string"
+}

addedInput schema / properties / tidecloakUrl

Added value: +{
+  "description": "Base URL. Default http://localhost:8080.",
+  "type": "string"
+}

AddedAug 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the upload contract (multipart parts, jpg/png/gif/webp allowlist with SVG rejected, 5 MB cap), the fact that set-branding both saves and re-signs, and the IGA exemption. The only soft spot is the framing 'BRAND ... upload them', which reads like a mutation even though the tool actually only emits a command — the readOnlyHint annotation is technically consistent with 'returns a command' but the description could state more plainly that the tool itself changes nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and information-dense, but it is a single sprawling block with heavy ALL-CAPS emphasis and long parentheticals (e.g. the entire contract clause) that make it harder to scan than it needs to be. The content largely earns its place, but the structure does not.

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

Completeness5/5

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

No output schema exists, yet the description fully explains what comes back: the runnable command, the verified upload contract, and fallback image-model prompts. For a zero-required-parameter helper tool, an agent has everything needed to call it and act on the 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the effect of the parameters ('Pass realm/accent/appName to get the command pre-filled') and confirming that all are optional convenience pre-fills rather than required inputs.

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?

Opens with a specific verb+resource ('BRAND THE ENCLAVE') and immediately clarifies the mechanics: it returns a ready-to-run command that generates, validates, uploads, and signs IdP settings. That distinguishes it sharply from siblings like tide_scaffold or tide_doctor, which do not deal with login-screen theming.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger ('CALL THIS whenever branding, a logo, a background, theming or "skinning" ... comes up') plus an explicit follow-through instruction ('then RUN the command; do not just describe it'). This is about as unambiguous as usage guidance gets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Raziel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.