Skip to main content
Glama

SkinKnowledgeBase Skincare Question and Answer MCP

by io.github.fulcrai

search

Read-onlyIdempotent

Search public SkinKnowledgeBase content. Required input: query string. Optional inputs: entity_type (Question, Concern, Ingredient, Product, SideEffect, Source), deprecated type alias, limit 1-50, and cursor. Returns compact ranked public results with canonical URLs, snippets, matched fields, scores, and public-safe retrieval metadata. Use for skincare questions, ingredient/product lookup, cited source lookup, and comparison-page discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoDeprecated alias for entity_type; kept for compatibility.
limitNo
queryYes
cursorNo
entity_typeNoPreferred entity type filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the SKB MCP tool call succeeded.
dataNoTool-specific public SkinKnowledgeBase response data.
metaNoResponse metadata for successful calls.
errorNoError details when ok is false.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context that results are compact, ranked, public-safe, and include metadata like snippets and scores, enhancing transparency 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences efficiently cover action, resource, inputs, outputs, and use cases with no redundant phrasing, front-loading the most critical information.

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?

Description covers purpose, parameters, output structure, and use cases. Given an existing output schema, it is mostly complete, though it omits details on pagination (how to use cursor) and query semantics (fuzzy matching, case sensitivity).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 40% schema description coverage, the description should add meaning for undocumented parameters (e.g., query, cursor, limit). It merely lists them without explaining query syntax, cursor usage, or limit behavior, failing to compensate for the gap.

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?

The description clearly states the tool searches public SkinKnowledgeBase content, lists optional filters, and specifies use cases covering multiple entity types, distinguishing it from sibling tools like search_entities and search_questions that are entity-specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides use-case examples (skincare questions, ingredient lookup, etc.) but does not explicitly contrast with alternatives or state when not to use this tool, leaving some ambiguity for an agent.

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

All SkinKnowledgeBase Skincare Question and Answer MCP toolsInspect
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.2/5.0
Disambiguation4/5

Most tools have distinct purposes, but the deprecated alias get_ranked_product_for_question and the overlap between fetch (generic ID) and get_entity (type+slug) create slight ambiguity.

Naming Consistency3/5

Naming mixes patterns: 'fetch' stands alone, while others use 'get_', 'search_', or 'list_'; the deprecated alias also deviates from the plural form of the newer tool.

Tool Count5/5

10 tools cover querying, searching, and listing without being too many or too few; appropriate for a read-only knowledge base.

Completeness5/5

The set provides full read coverage: generic fetch, typed entity retrieval, question bundles with optional includes, product rankings, sources, lists, and multiple search variants. No write operations are expected for this use case.

Resources