Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Search products and ingredients

inkeedecoder_search
Read-onlyIdempotent

Search a cosmetics database by product, brand, or ingredient name to get matching names, slugs, and URLs, one page at a time. Use returned slugs to open full product or ingredient details.

Instructions

Search INKEEDecoder (formerly INCIDecoder) for cosmetic products and ingredients by name. Returns names, slugs, and URLs — one page at a time. Pass a result's slug to inkeedecoder_get_product or inkeedecoder_get_ingredient for the full page. Read-only: it never modifies anything.

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": {
      "query": "<query>"
    },
    "name": "inkeedecoder_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoReturn only this tab. Omit it to get page 1 of both products and ingredients in a single request; with `tab` set, any page costs exactly one request.
pageNo1-based page number. Each response states whether another page is available.
queryYesProduct name, brand, or ingredient name — for example "squalane", "niacinamide", or "The Ordinary Retinol 1% in Squalane".

Output Schema

NameRequiredDescriptionDefault
tabNoPresent when `tab` was requested.
queryYesThe query that was run.
resultsNoMatches from the requested tab. Present when `tab` was set.
productsNoProduct matches. Present when no `tab` was requested.
ingredientsNoIngredient matches. Present when no `tab` was requested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the 'Read-only: it never modifies anything' sentence is largely redundant. The description does add genuine behavior beyond the annotations: the paginated, one-page-at-a-time retrieval model and the two-step search-then-fetch workflow. Return field details are largely covered by the output schema, so omitting them is acceptable.

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?

Four short sentences, front-loaded with purpose, then workflow, then pagination, then safety. Every sentence contributes something and nothing is padded.

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 input schema, an output schema, and rich annotations, the description covers purpose, pagination, and the downstream get_* workflow, which is enough to call it correctly. The one missing piece is differentiation from inkeedecoder_search_products, a sibling an agent would plausibly pick instead.

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%, with the tab enum and page semantics fully documented inline, so the schema already carries the parameter burden. The description adds no example values or constraints beyond what the schema states. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Search INKEEDecoder ... for cosmetic products and ingredients by name') and clarifies the legacy name INCIDecoder, so an agent knows exactly what it retrieves. It distinguishes itself from the get_* siblings by routing slugs onward, but it never explains how it differs from the sibling inkeedecoder_search_products, which is the most likely confusion point.

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?

Gives clear usage context: search first, then pass a returned slug to inkeedecoder_get_product or inkeedecoder_get_ingredient for the full page, and note that results come one page at a time. It stops short of explicit when-not guidance, and the existence of inkeedecoder_search_products leaves an unresolved choice the description does not resolve.

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