Skip to main content
Glama

Get product details

get_product
Read-onlyIdempotent

Fetch a single Kaspi.kz product's title, category, description, full specifications, photo count, and link by product ID to inspect core listing details.

Instructions

Read one product: title, category, description, full specifications, photo count and link. For prices use get_product_offers, for photos get_product_photos, for reviews get_product_reviews.

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
cityNoCity name, code or id (e.g. 'Алматы', 'almaty', '750000000'). Prices, sellers and delivery depend on it. Omit to use the configured default city. Ask the user where they are if it matters and is unknown.
product_idYesProduct id as returned by search_products.
marketplaceNoMarketplace id from list_marketplaces.kaspi

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/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. The description adds context the annotations do not: which fields are returned and that prices/photos/reviews are deliberately excluded from the payload. It does not mention auth needs, rate limits, or the city-dependent pricing caveat, but those are secondary here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the returned-field summary front-loaded and the sibling routing immediately after. Nothing is redundant or padded.

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 must signal return content, and it does by listing the fields delivered. All three parameters are covered by the schema. Only minor gaps remain, such as the absence of any note on error behavior for an unknown product_id.

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_id, city, marketplace) are already documented in the schema, including the city fallback and the note to ask the user. The description adds no parameter-level meaning beyond that, so 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 ('Read one product') and enumerates exactly what is returned: title, category, description, full specifications, photo count and link. It is clearly distinguishable from the sibling tools it names, so an agent can pick it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent elsewhere by task: prices go to get_product_offers, photos to get_product_photos, reviews to get_product_reviews. This is a direct when-to-use-this vs when-to-use-another statement, leaving little to inference.

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