Assess My Hair, powered by Rich Mom Recommends. Understand. Care. Thrive. Your personalized hair &am
Given a person’s hair type, current hair condition, goals, and routine, return COSMETIC hair-care approaches and product categories to consider. Cosmetic and educational only — it does NOT diagnose, treat, or advise on any medical or scalp condition, does NOT prescribe medication, and routes anything concerning to a qualified professional. No emails, purchases, or other consequential actions are triggered.
| Name | Required | Description | Default |
|---|---|---|---|
| goals | No | Cosmetic goals, e.g. ["length retention", "more moisture", "reduce breakage", "define curls"]. A single string is also accepted. | |
| routine | No | Current routine details (all optional): washFrequency, deepConditioning, heatUse, protectiveStyles, productCount. | |
| hairType | No | Hair type / texture, e.g. "4c coily", "type 3 curly", "fine wavy", "color-treated". | |
| condition | No | Current hair conditions/concerns, e.g. ["dry", "breakage", "frizz", "heat-damaged"]. A single string is also accepted. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the tool is cosmetic and educational only, does not diagnose or prescribe, routes concerning matters to professionals, and triggers no emails, purchases, or other consequential actions.
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?
The description is a compact two-sentence definition with no filler. The main purpose is front-loaded, and the safety and scope limitations are stated efficiently in the second sentence.
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?
The description is complete for this tool's complexity: it summarizes all inputs, states the output type, discloses limitations, and provides safety routing. Required parameters are 0, there is no output schema, and no siblings exist, so nothing essential is missing.
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 description coverage is 100%, so the parameters are already well-documented. The description mentions hair type, condition, goals, and routine at a high level, but adds no additional semantic detail beyond what the schema provides.
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?
The description states a specific verb ('return') and resource ('COSMETIC hair-care approaches and product categories to consider'), making the tool's function immediately clear. It also explicitly distinguishes itself from medical or diagnostic tools by defining the cosmetic/educational boundary.
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?
The description gives clear context: it is for cosmetic hair-care guidance based on hair type, condition, goals, and routine. It also provides exclusions by stating it does NOT diagnose, treat, or advise on medical/scalp conditions and routes concerning cases to a professional, though it does not name explicit alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
assess_hair_needsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Can AI confidently recommend your business? The AI Recommendation Readiness Audit shows whether your
AI-native beauty ads, sponsored product discovery, and brand recommendations.
Analyze user-submitted face photos with a complete report or 13 focused face-analysis tools.
8-dimension business diagnosis with Revenue Leak Score and triple-option recommendations
Add one secure layer between your agents and this server.
With only one tool, there is no ambiguity or overlap in tool selection; assess_hair_needs is the only possible choice. Its description clearly defines what it does and what it does not do.
The single tool name follows the conventional verb_noun snake_case pattern (assess_hair_needs), which is clear and predictable. There are no conflicting naming conventions to confuse an agent.
The server is a single-purpose assessment tool, so one tool is not necessarily wrong, but the surface feels thin for a hair-care domain. Supporting tools such as clarifying hair type or expanding product-category guidance would round it out.
The tool fully covers the core stated purpose of assessing hair needs and returning cosmetic approaches and product categories, so there are no major dead ends in the main workflow. Minor gaps exist only around follow-up refinement or more specific product guidance, which the tool explicitly disclaims.
