Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Get products containing an ingredient

inkeedecoder_get_ingredient_products
Read-onlyIdempotent

List cosmetic products containing a given ingredient on INKEEDecoder, with optional entries that declare the ingredient percentage and paginated results.

Instructions

List the cosmetic products on INKEEDecoder (formerly INCIDecoder) that contain a given ingredient — the reverse of a product page. Optionally include the products that declare the ingredient's percentage. Returns one page at a time. 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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIngredient slug, site path (/ingredients/...), or ingredient URL on inkeedecoder.com or incidecoder.com.
pageNo1-based page number. Each response states whether another page is available.
include_known_amountNoInclude the "products with a known amount" carousel (products that declare the percentage). Only present on page 1. Default false.

Output Schema

NameRequiredDescriptionDefault
productsYesProducts that list this ingredient.
knownAmountProductsNoProducts that declare the ingredient's percentage, when `include_known_amount` was set on page 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered; the description's 'Read-only' merely restates it. The one genuinely additive note is 'Returns one page at a time', though the page parameter's schema description already says each response reports whether another page exists.

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 short sentences, front-loaded with the core scope before the optional behavior and the read-only note. Nothing is padded and no sentence is redundant with the purpose statement.

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, 100% parameter coverage and complete annotations, the description only needs to orient the agent, which it does. Minor gaps remain: no indication of page size, result ordering, or the shape of the optional carousel.

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 all three parameters are already documented, including the accepted id formats and the page-1-only limitation of include_known_amount. The description's percentage note paraphrases the existing include_known_amount description rather than adding new meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('List the cosmetic products ... that contain a given ingredient') and explicitly frames it as 'the reverse of a product page', which cleanly separates it from inkeedecoder_get_ingredient and inkeedecoder_get_product.

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

Usage Guidelines4/5

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

The 'reverse of a product page' framing gives an agent a clear routing rule: go from ingredient to products, not product to ingredients. It also flags the optional percentage-declaring subset. It stops short of naming sibling alternatives or stating when not to use it.

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