Skip to main content
Glama
musaceylan

PriceAtlas MCP Server

by musaceylan

get_world_prices

Retrieve global price ranges for products across 27 countries using barcode data to compare international food costs.

Instructions

Get aggregated world prices for a product from Open Food Facts global database. Shows price ranges across countries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barcodeYesProduct barcode (8-14 digits)

Implementation Reference

  • The implementation of the get_world_prices MCP tool, which queries the Open Food Facts API for world prices based on a barcode.
    server.tool(
      'get_world_prices',
      'Get aggregated world prices for a product from Open Food Facts global database. Shows price ranges across countries.',
      { barcode: z.string().describe('Product barcode (8-14 digits)') },
      async ({ barcode }) => {
        try {
          const result = await api(`/api/world-prices?barcode=${barcode}`);
          return text(result);
        } catch (e) {
          return errorResult(`World prices failed: ${(e as Error).message}`);
        }
      },
    );
Behavior3/5

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

Discloses data source (Open Food Facts global database) and return format (price ranges across countries). However, as a read operation with no annotations, it should ideally confirm read-only nature, caching behavior, or error handling for invalid barcodes—none of which are mentioned.

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 precisely worded sentences. First establishes action and source, second clarifies return value. No redundant phrases or tautologies. Excellent information density.

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?

Adequate for a single-parameter lookup tool without output schema. Description compensates for missing output schema by stating what gets returned ('price ranges across countries'). Minor gap regarding error cases or specific data format, but sufficient for tool selection.

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 has 100% coverage with clear barcode description ('Product barcode (8-14 digits)'). Description references 'a product' which implicitly maps to the barcode parameter but adds no syntax, format, or constraint details beyond what the schema already provides. Baseline 3 appropriate given complete schema.

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?

Description uses specific verb 'Get' with resource 'aggregated world prices' and clarifies the scope (global database, across countries). Effectively distinguishes from sibling 'get_prices' by emphasizing geographic breadth and aggregation.

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?

Provides implicit context through 'world' and 'global database' wording that suggests use for international price comparison, but lacks explicit guidance on when to choose this over 'get_prices' or 'lookup_product'. No prerequisites or exclusions stated.

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