Skip to main content
Glama

Get product prices and sellers

get_product_offers
Read-onlyIdempotent

Lists seller offers for a product in a specified city, ordered by price with seller ratings and delivery options; an empty result means the product is unavailable there.

Instructions

List seller offers for a product in a city, cheapest first: seller, seller rating, price and delivery options. An empty list means the product is not available in that city.

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_offers"
  }
}

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.
pageNo0-based page number.
limitNoOffers per page.
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/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are sorted cheapest-first and an empty list is a definitive 'not available in this city' signal rather than an error. It stops short of noting pagination limits or that results are marketplace-scoped.

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 with no waste; the resource, ordering, and returned fields are front-loaded, and the empty-result caveat follows naturally.

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 return-value burden and does so by enumerating seller, rating, price, and delivery options. It covers the empty case but says nothing about how pagination behaves or whether the returned list is capped, which the page/limit defaults make relevant.

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 coverage is 100%, so product_id, city, page, limit, and marketplace are all documented in the schema itself, including the city-format examples and defaults. The description only echoes that a city scopes prices/sellers and adds the sort order, which is not a parameter behavior. Baseline 3 applies since the schema does the heavy lifting.

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 (list), resource (seller offers for a product), scope (in a city), and ordering (cheapest first), plus the exact fields returned. An agent can distinguish this from get_product, get_product_reviews, and get_product_photos purely from this sentence.

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 description gives result-interpretation guidance ('empty list means not available in that city') but never says when to prefer this over siblings like get_product or search_products. The only real usage steering ('omit to use the default city', 'ask the user where they are') lives in the city parameter's schema text, not the description.

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