Skip to main content
Glama

Listed price bands

price_bands
Read-only

Going prices for a product: median, middle half and median MOQ across all priced listings in matching product categories, with the US import duty where known, and declared_import_price: the unit price importers declared to Chile's customs for the same HS6 code from China. Give hs6 (your classification of the product) to get that declared price for the code too; it is the only price when no product category matches. Free; does not spend a search.

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": {
      "query": "<query>"
    },
    "name": "price_bands"
  }
}

Input Schema

NameRequiredDescriptionDefault
hs6NoThe six-digit HS code you'd classify the product under, e.g. 340600 for candles. Give it whenever you can: it adds the unit price importers declared to customs for that code, the only price when no product category matches.
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hs6
      Added value: +{
      +  "description": "The six-digit HS code you'd classify the product under, e.g. 340600 for candles. Give it whenever you can: it adds the unit price importers declared to customs for that code, the only price when no product category matches.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds real context beyond them: the result is free and does not consume a search budget, prices are drawn only from 'all priced listings in matching product categories', and hs6 becomes the sole price source when no category matches. It does not cover currency/units or what an empty result looks like.

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?

One dense but front-loaded sentence that puts the returned statistics first and the optional-parameter guidance second; every clause carries information. The nested clauses around hs6 make it slightly hard to scan, but nothing is wasted.

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 usefully enumerates the fields the caller will receive, including the enterprise-specific declared_import_price and its fallback semantics. Remaining gaps are units, currency, and zero-match behavior for a two-parameter read-only tool, which are minor.

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 50%: hs6 is well documented in the schema and the description only reinforces it. The required 'query' parameter has no description anywhere — the phrase 'for a product' and 'matching product categories' hints that it is the product classification input, but format and matching behavior are left to inference.

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 names a specific resource (going prices for a product) and enumerates the exact statistics returned — median, middle half, median MOQ, US import duty, and declared_import_price. It is clear what the tool produces, but it never names a sibling or states how it differs from product_market or search_listings.

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?

'Give hs6 ... it is the only price when no product category matches' tells the agent when the optional parameter matters, and 'Free; does not spend a search' is a useful cost hint for deciding whether to call it. However, there is no guidance on when to choose this tool over the price-bearing siblings, so usage is only implied.

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