Skip to main content
Glama

SkinKnowledgeBase Skincare Question and Answer MCP

by io.github.fulcrai

get_entity

Read-onlyIdempotent

Fetch one public SkinKnowledgeBase entity. Required inputs: type (Question, Concern, Ingredient, Product, SideEffect, or Source) and slug_or_id (entity slug or ULID). Returns public entity details, canonical URL, text, and linked source/context fields where available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
slug_or_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 already declare read-only and safe behavior. Description adds that entity must be public and details what is returned (canonical URL, text, linked fields), beyond annotation cues.

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, front-loaded with purpose, then required inputs, then outputs. No redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity (2 params, output schema exists), description covers purpose, inputs, and output fields sufficiently. No missing critical information.

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

Parameters4/5

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

Schema coverage 0%, but description compensates by explaining type enum values and slug_or_id as slug or ULID, and notes they are required. Adds clarity beyond the raw schema.

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 uses specific verb 'Fetch' and resource 'one public SkinKnowledgeBase entity', clearly distinguishes from siblings like list_entities and search_entities by specifying entity type and identifier.

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?

Implies usage for fetching a single entity by type and slug/ID, but no explicit when-to-use vs alternatives like search or get_question_bundle.

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