Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Switch profile

use_brand
Idempotent

Pin which brand profile this connection acts on by passing a profile ID or exact name from list_brands. Works for your own and shared accounts, then persists for this API key until changed.

Instructions

Pin which profile this connection acts on. Pass the profile id or exact name from list_brands. Works for your own profiles AND one another account SHARED with you (pass its name or the profile id list_brands prints); access is verified against your real membership before it is pinned. Persists for this API key until changed, on every surface (hosted connector included — no environment variables, no restart).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYesprofile id (e.g. default / p_xxx), its exact name from list_brands, or the profile id of one shared with you

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"brand id (e.g. default / p_xxx), its exact name from list_brands, or the profile id of a workspace shared with you"New value: +"profile id (e.g. default / p_xxx), its exact name from list_brands, or the profile id of one shared with you"
  2. Changed2 schema fields changedv0.1.161
    • changedInput schema / properties / brand / description
      Previous value: -"brand id (e.g. default / p_xxx) or its exact name from list_brands"New value: +"brand id (e.g. default / p_xxx), its exact name from list_brands, or the profile id of a workspace shared with you"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "brand": {
-      "description": "the now-active brand ({id, name})"
-    },
-    "ok": {
-      "description": "true when the brand switch persisted",
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, idempotent mutation. The description adds real behavioral context: membership is verified before pinning, the pin persists for this API key until changed, it applies on every surface including the hosted connector, and no env vars or restart are needed. This is exactly the extra disclosure annotations can't carry.

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 the core action and the argument format. Mild redundancy: the 'name or profile id from list_brands' instruction is repeated in the second clause, and the parenthetical asides add length, though each conveys distinct behavior.

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?

For a single-parameter, no-output-schema tool, the description covers everything needed: what is mutated (the pinned profile), accepted argument forms, the source for valid values, permission verification, and persistence scope. Nothing an agent needs to call it correctly is missing.

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 already 100%, and the description goes further by enumerating accepted forms (profile id like default/p_xxx, exact name, or the id of a profile shared with you) and pointing to list_brands as the source of valid values, which the schema alone does not.

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 precise verb+resource: 'Pin which profile this connection acts on.' An agent can immediately tell this is a context-switch operation, distinct from list_brands / create_brand / update_brand / delete_brand / get_brand siblings.

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 source for the argument ('the profile id or exact name from list_brands') and explicitly extends use to profiles shared with the account, so the agent knows both valid scenarios. It stops short of stating when *not* to call this (e.g. relative to get_brand or per-call brand args).

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