Skip to main content
Glama
musaceylan

PriceAtlas MCP Server

by musaceylan

get_prices

Retrieve product price observations and statistics by barcode, with optional country filtering. Provides individual price data and aggregated metrics like minimum, average, and count per country.

Instructions

Get price observations and stats for a product. Optionally filter by country. Returns individual observations and min/avg/count stats per country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barcodeYesProduct barcode (8-14 digits)
countryNo2-letter country code (e.g. "DE", "TR", "US")

Implementation Reference

  • Tool registration and handler implementation for "get_prices" in src/index.ts. It performs a GET request to the price atlas API.
    server.tool(
      'get_prices',
      'Get price observations and stats for a product. Optionally filter by country. Returns individual observations and min/avg/count stats per country.',
      {
        barcode: z.string().describe('Product barcode (8-14 digits)'),
        country: z.string().length(2).optional().describe('2-letter country code (e.g. "DE", "TR", "US")'),
      },
      async ({ barcode, country }) => {
        try {
          let path = `/api/prices?barcode=${barcode}`;
          if (country) path += `&country=${country}`;
          const prices = await api(path);
          return text(prices);
        } catch (e) {
          return errorResult(`Get prices failed: ${(e as Error).message}`);
        }
      },
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context by disclosing the return structure (individual observations plus min/avg/count aggregations per country), which compensates for the missing output schema. However, it omits operational details such as error behavior (e.g., invalid barcode handling), rate limits, or caching behavior.

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?

The description consists of three efficient sentences with zero waste: purpose declaration, filtering option, and return value disclosure. The information is front-loaded and logically sequenced, making it easy to parse.

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?

Given the absence of an output schema, the description appropriately discloses the return structure (observations and stats). For a read-only tool with simple parameters, this is nearly complete. It could be improved by mentioning error conditions (e.g., invalid barcode format or not found), but the essential information is present.

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?

With 100% schema description coverage, the baseline is 3. The description adds minimal semantic value beyond the schema—primarily labeling the country parameter as an 'optional filter,' which clarifies its functional role. The barcode parameter semantics are adequately covered by the schema alone.

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 uses a specific verb ('Get') and clearly identifies the resource (price observations and stats) and scope (for a product). It effectively distinguishes from write-oriented sibling 'submit_price' and implies single-product lookup via the barcode parameter. However, it does not explicitly differentiate from the closely named sibling 'get_world_prices', leaving ambiguity about when to use which.

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 implies usage through the phrase 'Optionally filter by country,' suggesting when to apply the filter parameter. However, it provides no explicit guidance on when to use this tool versus close siblings like 'get_world_prices' (global vs. per-product) or versus 'search_products' (fuzzy search vs. barcode lookup).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musaceylan/priceatlas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server