Skip to main content
Glama

SkinKnowledgeBase Skincare Question and Answer MCP

by io.github.fulcrai

fetch

Read-onlyIdempotent

Fetch one public SkinKnowledgeBase resource. Required input: id, which may be a canonical SKB URL, public comparison URL, entity ULID, slug, or accepted comparison-page identifier. Returns public read-only text and structured data such as title, canonical URL, entity type, evidence sources, product fact sources, updated_at, and public-safe comparison metadata where applicable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

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

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint. Description adds context about returning public read-only text and structured data, and lists specific fields. No contradictions; enhances 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?

Two sentences: first states purpose, second details return type. No wasted words; front-loaded with key action and required input.

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 presence of output schema, description adequately lists return fields. Might benefit from mentioning behavior when id not found, but overall sufficient for a straightforward fetch tool.

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

Parameters5/5

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

Schema coverage is 0%, but description thoroughly explains the id parameter: accepts canonical SKB URL, public comparison URL, entity ULID, slug, or accepted comparison-page identifier. Adds significant meaning beyond schema constraints.

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 fetching one public SkinKnowledgeBase resource, specifies verb and resource type, and lists returned elements. Differentiates from siblings like search or list by focusing on single resource retrieval.

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?

Mentions required input id and acceptable formats, but does not explicitly say when to use this tool versus alternatives like get_entity or search. Implied use for known identifiers.

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