Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get saved profile

get_brand
Read-onlyIdempotent

Check if a brand profile is on file for the active profile; retrieve saved products, logos, palette, positioning, and memory. If none exists, onboard with draft_brand before using create tools.

Instructions

What Hermoso ALREADY KNOWS for the active profile: the same saved profile (products, logos, palette, positioning) + learned memory the web Studio uses. Call it when you need to know whether a brand is on file: if hasBrand is true you can omit brand everywhere; if false, onboard with draft_brand. Not a required first step before a render: the create tools read the saved brand by themselves. 0 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoprofile id/name from list_brands, this call only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"brand id/name from list_brands, this call only"New value: +"profile id/name from list_brands, this call only"
  2. Changed1 schema field changedv0.1.371
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "brand id/name from list_brands, this call only",
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "brand": {
-      "description": "the saved brand profile (name, domain, category, products, palette, …) or null"
-    },
-    "hasBrand": {
-      "description": "whether a brand is saved for this workspace",
-      "type": "boolean"
-    },
-    "memoryCount": {
-      "description": "how many learned memory notes the workspace holds",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Addedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds the cost signal (0 credits) and the important behavioral fact that create/render tools auto-read the saved brand, meaning this call is often unnecessary. It stops short of describing the exact response shape, but adds real context beyond annotations.

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?

Front-loaded with what the tool returns, then routing guidance, then the exclusion. Dense but every clause earns its place; slightly verbose in the framing of the hasBrand branch, but no filler.

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?

No output schema exists, yet the description still enumerates the returned payload (products, logos, palette, positioning, learned memory) and references the hasBrand field an agent needs to act on. Complete enough for a single-param read tool, with only the precise field structure left implicit.

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% and the single 'brand' parameter is already documented as a profile id/name from list_brands scoped to this call only. The description reinforces the 'active profile' concept but adds no format or syntax beyond the schema, so baseline 3 applies.

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+resource (retrieves the saved brand profile for the active profile) and enumerates what it contains: products, logos, palette, positioning, plus learned memory. It is clearly distinguishable from siblings like list_brands, create_brand, draft_brand, and use_brand, which it either names or implicitly contrasts.

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 when-to-use (check whether a brand is on file), the branching consequence (if hasBrand is true omit brand everywhere; if false onboard with draft_brand), and an explicit when-NOT (not a required first step before a render, because the create tools read the saved brand themselves). Alternatives are named directly.

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

Deploy Server

Other Tools