Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Get a brand's products

inkeedecoder_get_brand
Read-onlyIdempotent

Fetch a brand page and its product catalogue from INKEEDecoder one page at a time by passing a brand slug, /brands/ path, or inkeedecoder.com/incidecoder.com URL.

Instructions

Fetch a brand page from INKEEDecoder (formerly INCIDecoder) and its catalogue of products, one page at a time. Accepts a slug, a /brands/ path, or an inkeedecoder.com or incidecoder.com URL. 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_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrand slug, site path (/brands/...), or brand URL on inkeedecoder.com or incidecoder.com. The slug is the last segment of the page URL.
pageNo1-based page number. Each response states whether another page is available.

Output Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL on the site.
nameYesBrand name.
pathYesSite-relative path.
slugYesBrand slug.
productsYesThis page of the brand's products.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally; "Read-only" largely restates that. What the description does add beyond annotations is the pagination behavior (results arrive one page at a time), but it omits failure behavior for invalid slugs or unknown brands and any rate/limit context for a network-backed fetch.

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?

Two tight sentences with the capability front-loaded and the input formats immediately after; nothing is buried. The closing "Read-only" is the one redundant clause given readOnlyHint is already set in annotations.

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 an output schema present, return shape need not be explained, and pagination plus accepted identifier formats cover the main call-time questions. Missing only edge-case behavior (invalid slug, brand not found, last page) to be fully complete for a network-backed fetch tool.

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 both parameters are documented there, including the slug/path/URL forms and the 1-based page semantics, so the schema does the heavy lifting. The description's sentence about accepted input forms duplicates the schema rather than adding new meaning such as slug normalization or what happens on a mismatch.

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 concrete verb and resource: fetches a brand page plus its product catalogue, paginated. This is clearly distinct from get_product and get_ingredient_products by resource scope, though the description never names a sibling to sharpen the boundary 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?

"One page at a time" implies the caller must iterate pages, and the accepted input forms tell the agent what it can pass. There is no explicit when-to-use versus when-not guidance, e.g. whether to resolve a brand name via inkeedecoder_search first or whether search_products is the better entry point for cross-brand queries.

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