MHS BLOOM — Neutral Skincare Reference
Server Details
Query an independent, payment-blind reference of 1,682 dermacosmetic products — by product, ingredient, concern, category or brand. Neutral descriptive facts, every result links back to its reference page. No ratings, no paid placement.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolsfind_alternativesFind neutral alternatives in the same categoryAInspect
Given a product, return other products in the SAME category from the catalog, listed neutrally (alphabetical, never ranked). This is discovery, not a recommendation — the personal best-fit and price-tiered alternatives live in the app.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The product to find alternatives for. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Discloses that results are alphabetical, never ranked, and that it's discovery. Could mention handling of missing products or result limits, but adequate for a simple retrieval tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, no fluff. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple schema and no output schema, description covers behavior well: return other products in same category, alphabetical, not ranked. Could mention whether it excludes the input product itself, but overall complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with description for the single parameter. Description adds that the tool finds products in the same category, which adds meaning beyond the schema's 'The product to find alternatives for.'
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states verb (return), resource (other products in the same category), and adds nuance (alphabetical, not ranked). Differentiates from sibling tools like search_products and personal best-fit alternatives in the app.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly notes that this is for discovery, not recommendation, and that personal best-fit alternatives live in the app. Provides when-not-to-use context but does not name specific sibling tools as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_brandsList the brands coveredInspect
List the dermacosmetic brands covered in MHS BLOOM's reference, with how many products each has.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
lookup_productLook up a skincare productInspect
Identify a dermacosmetic product in MHS BLOOM's neutral reference and return its descriptive facts (brand, key ingredients, the concerns it's oriented toward, texture, fragrance, price band, who it's aimed at) plus a link to its reference page. Descriptive only — not a personal skin verdict.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Product name and/or brand, e.g. "CeraVe foaming cleanser". |
search_productsSearch products by ingredient / concern / category / brandInspect
Search MHS BLOOM's reference for products by any of: key ingredient (e.g. "niacinamide"), skin concern (e.g. "blemishes"), category (e.g. "sunscreen"), brand, and/or fragrance_free. Returns a neutral, alphabetical list with reference links. Never ranked or rated.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | ||
| limit | No | Max results (default 15, max 40). | |
| concern | No | ||
| category | No | ||
| ingredient | No | ||
| fragrance_free | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!