Skip to main content
Glama

get_kohls_stock

Read-onlyIdempotent

PAID. Live Kohl's per-UPC (per-variant) stock counts for a batch of Kohl's products. Pass products as an array of Kohl's PDP URLs and/or bare "prd-" web IDs (affiliate/redirect links are followed server-side to the canonical kohls.com PDP). Returns one row per product with status ("ok" or "stock_unavailable"), total_in_stock (sum of online-available units across variants), and a variants[] breakdown (upc, sku, qty, availability, in_stock). Counts are a live snapshot and move constantly. stock_unavailable means the fetch fleet could not read the page (Akamai challenge / delisted / no stock JSON) — it is NOT a zero count; never turn it into 0. Send at most 100 products per call and loop in chunks for longer lists. Kohl's only. Requires a paid plan (mcp_standard, mcp_pro, or enterprise_api).

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": {
      "products": "<products>"
    },
    "name": "get_kohls_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesKohl's PDP URLs and/or bare "prd-<id>" web IDs. 1-100 per call; chunk longer lists across multiple calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent, but the description adds the critical semantics: `stock_unavailable` is a fetch failure, not a zero, and must never be coerced to 0; counts are a live snapshot that moves; affiliate/redirect links are followed server-side; and access requires a paid plan tier.

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?

Front-loaded with 'PAID' and the core purpose, then error semantics and limits. Some repetition of the 100-item cap already in the schema, but every sentence carries operational weight.

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?

No output schema exists, yet the description fully specifies the return shape (`status`, `total_in_stock`, `variants[]` with upc/sku/qty/availability/in_stock) plus the failure-mode interpretation and batch limit — everything needed to call and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents the array, so the baseline is 3; the description goes further by explaining accepted input forms and that affiliate/redirect URLs are resolved to canonical PDPs server-side, which is behavior the schema does not convey.

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 — live per-UPC Kohl's stock counts for a batch of products — with scope ('Kohl's only') that separates it from retailer-agnostic siblings like get_retailer_product or search_retailer_products.

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 concrete operating conditions: max 100 products per call, loop in chunks for longer lists, Kohl's-only scope, and a paid-plan requirement. It does not explicitly name a sibling alternative for other retailers, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources