Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Search products by ingredient

inkeedecoder_search_products
Read-onlyIdempotent

Search cosmetic products by name and required or forbidden ingredients, such as moisturizers with squalane and no fragrance, returning one page at a time with next-page availability.

Instructions

Search INKEEDecoder for cosmetic products using the advanced filter: match a name and/or require and forbid specific ingredients. Use it for questions like "moisturizers with squalane and no fragrance". Returns one page of products — each response says whether another page is available. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Each response states whether another page is available.
queryNoFree-text part of the search: a product or brand name. Leave empty to filter purely by ingredients — but then pass `include` or `exclude`.
excludeNoIngredients the product must not contain, using the site's display names — for example ["Fragrance", "Alcohol Denat."].
includeNoIngredients the product must contain, using the site's display names — for example ["Squalane", "Tocopherol"]. Take these from an ingredient page's name, not from an INCI list.
include_modeNo`all` (default) requires every `include` ingredient; `any` requires at least one.all

Output Schema

NameRequiredDescriptionDefault
pageYes1-based page number of this page.
itemsYesResults on this page.
hasMoreYesWhether another page is available.
nextPageUrlNoURL of the next page, present when hasMore is true.

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?

The description states 'Read-only', which merely repeats readOnlyHint=true and deserves no credit. It does add the result-shape behavior — one page per call, with the response indicating whether another page exists — but that same fact is already carried by the `page` parameter description in the schema, so the marginal value is modest.

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: filter purpose, concrete use case, then result behavior. Efficient overall, with only the pagination sentence duplicating what the schema already says about page handling.

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 100%-covered schema and an output schema, the description is not obliged to explain return values, and it does cover the filter model, the empty-query caveat, and paging. The one real gap is the absence of routing guidance against inkeedecoder_get_ingredient_products and inkeedecoder_search.

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 restates the include/exclude pairing constraint ('leave empty to filter purely by ingredients — but then pass include or exclude'), which is genuine cross-parameter meaning, but the ingredient-name examples and include_mode semantics are already fully documented in the schema.

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?

Specific verb+resource: 'Search INKEEDecoder for cosmetic products using the advanced filter', with the two filter axes spelled out (name query, required/forbidden ingredients). It does not, however, distinguish itself from the sibling inkeedecoder_get_ingredient_products, which an agent could plausibly pick instead for an ingredient-driven product lookup.

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?

Usage is conveyed by example ('moisturizers with squalane and no fragrance') and by the note that an empty query must be paired with include or exclude. There is no explicit when-to-use/when-not guidance relative to the sibling tools, so the agent must infer which product-search entry point to take.

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