Apostle — AI Men's Skincare Commerce

skincare_recommend

Read-only

(Deprecated: use 'recommend' instead. Works identically.) Get a personalized Apostle product recommendation with ingredient-aware scoring, safety notes, and routine building. Use when the user wants advice on what to buy, needs help choosing between products, has a specific skin concern (acne, aging, dryness, sensitivity, etc.), wants a routine, or asks "what should I use for X." Do not use for browsing or listing products — use search_products instead. Returns scored products with explanations, usage instructions, and Shopify checkout. This tool analyzes ingredients, irritation risk, and product compatibility — use it over search_products when the user needs guidance, not just a product list.

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	No	Filter to a specific brand only (e.g. 'Glossier', 'CeraVe', 'The Ordinary'). Use when the user asks for products from a specific brand.
`query`	Yes	Natural language query about skin concerns (e.g. 'I have oily acne-prone skin and want something gentle under $30')
`strategy`	No	Optional offer strategy override: starter, gentle, budget, glow_safe, minimal, strong, fallback

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. Description adds value by explaining it analyzes ingredients, irritation risk, and product compatibility, and returns scored products with explanations and checkout. No contradictions.

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?

Description is comprehensive yet efficient, starting with deprecation notice, then purpose, usage guidelines, and behavioral details. Each sentence serves a purpose, though slightly verbose with redundant clarification.

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?

Given the 3 parameters, no output schema, and annotations present, the description covers the tool's purpose, usage context, return value (scored products with explanations), and sibling differentiation. Could hint at pagination or limits but adequate for decision-making.

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 has 100% coverage with detailed descriptions for all three parameters. Description does not add significant parameter-specific information beyond what schema provides, though it reinforces the natural language use case for query.

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?

Description clearly states the tool provides personalized product recommendations with ingredient-aware scoring, safety notes, and routine building. It explicitly distinguishes from siblings like search_products (for browsing) and recommend (deprecation alias).

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?

Explicitly states when to use (user wants advice, has skin concerns, needs routine) and when not to use (browsing/listing products, directs to search_products). Also identifies the replacement tool (recommend) due to deprecation.

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

All Apostle — AI Men's Skincare Commerce tools Inspect

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

A4/5.0

Disambiguation3/5

Most tools have distinct purposes, but there is clear overlap between 'recommend' and the deprecated 'skincare_recommend', and 'shop' as a routing tool could be ambiguous with 'search_products' and 'recommend'. Descriptions help but are not fully disambiguating.

Naming Consistency2/5

Naming patterns are inconsistent: some use verb_noun (e.g., check_inventory, compare_products), while others are single words (shop) or use a noun prefix (skincare_cart, skincare_recommend). The deprecated duplicate 'skincare_recommend' further disrupts consistency.

Tool Count5/5

14 tools is well within the 3-15 range and covers the necessary functions for a skincare commerce server: product lookup, search, recommendation, comparison, compatibility, inventory, checkout, deals, research notes, and issue reporting. No excess or deficiency.

Completeness4/5

The tool set covers core commerce workflows: browsing, product details, recommendations, checkout, deals, and compatibility checks. Minor gaps exist (e.g., order history or user profile management) but are outside the apparent scope. The deprecated duplicate is a minor inefficiency.

Resources

Need Help?