Skip to main content
Glama

Raziel

by io.github.tide-foundation

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmNoRealm to brand, e.g. 'myapp'. Fills in the command.
accentNoHex accent colour without '#', e.g. '2f6f4e'. Default 1f6feb.
appNameNoApp name. Deterministically varies the mark's geometry so realms look distinct.
tidecloakUrlNoBase URL. Default http://localhost:8080.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • 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"
+}
  2. Added

TDQS

A3.8/5.0
Behavior1/5

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

Annotation contradiction: readOnlyHint=true but the description explicitly states it 'uploads both' files and 'saves+signs the IdP settings', and mentions 'set-branding = save AND re-sign'. This is a write/mutation operation, directly contradicting the read-only annotation.

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?

The description is long but front-loaded with the core purpose and each sentence adds functional detail (returns a command, validation, upload contract, prompts). It is slightly verbose but not wasteful; the length is justified by the tool's complexity.

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?

The description is highly complete for a complex tool: it explains the generated outputs (ready-to-run command, verified upload contract, image-model prompts), validation criteria, upload specs, and security exclusions. No output schema exists, so the description fully carries the burden of explaining return values and constraints.

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% with descriptions for all four parameters. The description adds context by saying 'Pass realm/accent/appName to get the command pre-filled' and details upload constraints like 'SVG REJECTED' and '5 MB cap', enriching the parameter semantics beyond the schema.

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?

The description leads with a clear, specific verb+resource: 'BRAND THE ENCLAVE FOR THE USER — generate a logo + background and upload them'. It explicitly covers branding, logo, background, theming, and skinning, and the 'CALL THIS whenever...' line distinguishes it from siblings by scoping its use case.

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 description gives an explicit trigger: 'CALL THIS whenever branding, a logo, a background, theming or \'skinning\' the enclave or login screen comes up'. It also instructs to 'RUN the command; do not just describe it'. However, it does not mention when not to use it or name alternative tools.

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

All Raziel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: reading specific document types (adapter, canon, gaps, playbook, etc.), performing assessments (blast_radius, security_analysis), branding, deployment decision, and listing content. However, some reading tools like tide_canon and tide_gaps could be confused, and the multiple scenario-related tools (scenario, bootstrap, manifest, roles) require careful reading of descriptions to differentiate.

Naming Consistency4/5

All tools use the 'tide_' prefix with snake_case, which provides a strong pattern. However, the naming mixes nouns (tide_canon, tide_gaps) with verb phrases (tide_choose_playbook, tide_list), and some tools like tide_dpop_asset are less intuitive. The pattern is mostly consistent but not strictly verb_noun.

Tool Count3/5

With 19 tools, the set is on the higher end for a single server. While many are necessary for the broad scope of reading various reference materials and performing analyses, the count feels slightly excessive. A few tools could be consolidated or removed to improve focus.

Completeness4/5

The tool surface covers reading all major reference documents, performing security assessments, branding, deployment decisions, and scenario matching. For the stated purpose of a 'Tide agent pack', it appears comprehensive. Minor gaps might include a tool for overall system health or status, but the core workflows are well-covered.

Resources