Skip to main content
Glama
shoper-mcp

shoper-mcp

by exelmedia

Szczegóły produktu / Get product

get_product
Read-onlyIdempotent

Retrieve read-only product details by ID, including prices, stock, categories, producer, codes, and a cleaned truncated description for catalog lookups.

Instructions

PL: Zwraca szczegóły jednego produktu po ID: nazwa, kody, ceny, stan, kategorie, producent, opis (oczyszczony z HTML, przycięty). Tylko odczyt. EN: Returns one product by ID (read-only), description stripped of HTML and truncated.

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_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesID produktu / product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral value beyond them by disclosing that the description field is HTML-stripped and truncated — a transformation that affects the returned data and cannot be inferred from annotations. It does not say how aggressive the truncation is, keeping it from a 5.

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?

Content is front-loaded with the core action and then the field inventory, with no filler or hedging. The Polish/English duplication roughly doubles the length, which is defensible for a bilingual server but is still redundant text in a single field.

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 no output schema, the description carries the burden of describing returns and does so by listing the returned fields plus the HTML-stripping/truncation behavior. Missing details such as truncation limits or error behavior for an unknown ID are minor for a simple single-record getter.

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?

Only one parameter exists and the schema documents it at 100% coverage ("ID produktu / product id", integer, >0), so the schema carries the semantics. The description's 'po ID' / 'by ID' confirms the parameter's role but adds nothing the schema lacks; baseline 3 applies.

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 ("Zwraca szczegóły jednego produktu po ID") and enumerates the returned fields (name, codes, prices, stock, categories, producer, description). This clearly separates it from list/search siblings like search_products and get_stock, which operate on sets or a different resource.

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?

Usage is only implied: 'by ID' signals a single-record lookup, so an agent can infer it is not the tool for browsing or querying. There is no explicit when-to-use or when-to-prefer-search_products guidance, and 'Tylko odczyt' is a safety statement rather than a usage rule.

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