Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Get an ingredient

inkeedecoder_get_ingredient
Read-onlyIdempotent

Fetches cosmetic ingredient details from INKEEDecoder, including function, rating, irritancy, and comedogenicity, with optional CosIng data, long-form writeup, and references.

Instructions

Fetch a cosmetic ingredient page from INKEEDecoder (formerly INCIDecoder): what it does, INKEEDecoder's rating, irritancy and comedogenicity, and optional CosIng identifiers, long-form writeup, and references. Accepts a slug, an /ingredients/ path, or an inkeedecoder.com or incidecoder.com URL. The long writeup is off by default. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "inkeedecoder_get_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIngredient slug, site path (/ingredients/...), or ingredient URL on inkeedecoder.com or incidecoder.com. The slug is the last segment of the page URL. Get one from inkeedecoder_search or a product's ingredient list.
imageNoInclude the ingredient's image URL. Default true.
proofNoInclude the reference list cited by the writeup. Default false.
cosingNoInclude CosIng data: CAS number, EC number, IUPAC name, and official functions. Default false.
safetyNoInclude irritancy and comedogenicity ratings. Default true.
detailsNoInclude the long-form writeup. Default false — it is several thousand characters per ingredient, so ask for it only when the answer needs the detail.
functionsNoInclude what the ingredient does, as /ingredient-functions/ links. Default true.
also_calledNoInclude the "also-called" alias. Default true.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
pathYes
slugYes
imageNo
proofNo
cosingNo
detailsNo
ourTakeYesINKEEDecoder's editorial rating, or null if none is shown.
functionsNo
irritancyNo
alsoCalledNo
comedogenicityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the closing "Read-only" sentence repeats structured data rather than adding to it. The genuinely useful behavioral detail—that the long writeup is opt-in and costly in payload size—is also stated in the schema, so the description contributes little new context beyond field defaults.

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?

Three front-loaded sentences: payload contents first, accepted identifier formats second, default behavior third. The trailing "Read-only." fragment is redundant with annotations and is the one phrase that does not earn its place.

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?

With a full output schema, complete parameter documentation, and rich annotations, the description covers enough for correct invocation. The only gap is error behavior for an unresolvable slug or URL, and that is a minor omission given the surrounding structured data.

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 description coverage is 100%, so the baseline is 3. The description names the categories of optional data (CosIng identifiers, long-form writeup, references) and the accepted input forms, but adds no syntax, normalization, or fallback detail beyond what each property already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetch a cosmetic ingredient page from INKEEDecoder" is a specific verb+resource, and the sentence enumerates exactly what comes back (rating, irritancy, comedogenicity, CosIng, writeup, references). It does not explicitly route against siblings such as inkeedecoder_get_ingredient_function or inkeedecoder_get_ingredient_products, so an agent must infer the boundary from the resource name alone.

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 implies usage (look up one ingredient, given a slug, /ingredients/ path, or site URL) and notes the writeup is off by default, which nudges toward the cheap call. It gives no explicit when-not guidance or named alternative for the deeper sibling endpoints.

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