Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Get an ingredient function

inkeedecoder_get_ingredient_function
Read-onlyIdempotent

Fetch an INKEEDecoder ingredient-function page to learn what a function means and which ingredients serve it. Accepts a slug, path, or URL and returns one page of results.

Instructions

Fetch an ingredient-function page from INKEEDecoder (formerly INCIDecoder) — what the function means and which ingredients serve it (for example "emollient"). Accepts a slug, an /ingredient-functions/ path, or an inkeedecoder.com or incidecoder.com URL. Returns one page of ingredients 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_function"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIngredient-function slug (for example "emollient", "antioxidant"), site path (/ingredient-functions/...), or URL on inkeedecoder.com or incidecoder.com.
pageNo1-based page number. Each response states whether another page is available.

Output Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL on the site.
nameYesDisplay name, for example "Emollient".
pathYesSite-relative path.
slugYesIngredient-function slug.
descriptionNoWhat the function means, when the page has an explanation.
ingredientsYesThis page of ingredients serving this function.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the trailing 'Read-only' sentence adds nothing. The one genuinely additive behavioral detail is 'Returns one page of ingredients at a time', which tells the agent results are paginated, but error behavior for an unresolvable slug/path/URL is unstated.

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?

It is front-loaded with the verb and resource, then input formats, then pagination — a sensible order, and every sentence is short. The closing 'Read-only' is the one wasted clause since annotations already carry that fact.

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?

With only two parameters, an output schema present, and annotations covering the safety and openness profile, the description covers what an agent needs to select and call it: the resource's meaning, the three accepted input forms, and pagination. Nothing material is left for the caller to guess about invocation.

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% and the schema already documents the accepted id forms (slug, /ingredient-functions/ path, inkeedecoder.com or incidecoder.com URL) and the page parameter's 1-based semantics with next-page signaling. The description restates the same three input forms rather than adding format or validation detail, so the baseline of 3 applies.

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?

The description names a specific verb ('Fetch') and resource ('ingredient-function page') and explains what that resource contains — what the function means and which ingredients serve it, with the concrete example "emollient". This clearly separates it from a per-ingredient lookup, though it never names a sibling tool to route against explicitly.

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 context in which the tool is useful is implied by 'what the function means and which ingredients serve it', which tells an agent the shape of the question it answers. There is no explicit when-not guidance and no named alternative (e.g., inkeedecoder_get_ingredient for a single ingredient) to disambiguate the choice.

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