Skip to main content
Glama
shoper-mcp

shoper-mcp

by exelmedia

Stany i ceny / Stock and prices

get_stock
Read-onlyIdempotent

Retrieve stock levels and prices for up to 50 selected products, including variants, from a Shoper store catalog. Read-only; purchase prices are excluded.

Instructions

PL: Stany magazynowe i ceny dla 1-50 produktów (także warianty). Bez ceny zakupu. Tylko odczyt. EN: Stock levels and prices for 1-50 products, including variants. No purchase price. 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": {
      "product_ids": "<product_ids>"
    },
    "name": "get_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNumer strony od 1 / page number, starting at 1
limitNoWierszy na stronę / rows per page
product_idsYesLista ID produktów / product ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, and destructiveHint=false, so the 'Read-only / Tylko odczyt' sentence repeats structured data. The genuinely additive part is the output-scope exclusion 'No purchase price', which tells the agent this cannot be used for cost data. However, it stays silent about pagination behavior even though 'limit' caps at 50 rows per page and 'page' goes to 1000, which matters for a batch tool covering up to 50 products.

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?

Both language versions are front-loaded with the core capability and the exclusion in three short sentences, with no wasted filler. The bilingual duplication doubles the raw length, but that is deliberate for a PL/EN audience rather than padding.

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?

For a read-only batch lookup whose annotations fully cover the safety profile and whose schema fully documents parameters, the description covers the essentials: what is returned, the scale limit, and the key exclusion. The only reasonable omission is pagination, and with no output schema an agent can discover that from the page/limit fields.

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 all three parameters (product_ids, page, limit) are already documented with types and bounds. The description only echoes the 1-50 item bound on product_ids and adds nothing about page/limit semantics, so baseline 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 states a specific verb and resource: retrieving stock levels and prices for 1-50 products including variants, plus an explicit scope exclusion (no purchase price). It is clear what data comes back, though it never contrasts itself with get_product for single-product lookups, so sibling differentiation is left to inference.

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 '1-50 products' bound plus the required product_ids parameter implies a batch-lookup-by-ID use case, but there is no explicit when-to-use or when-not-to-use guidance. It never says to prefer get_product for single items or search_products for discovery, so the agent must guess which sibling to reach for.

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