Skip to main content
Glama
musaceylan

PriceAtlas MCP Server

by musaceylan

submit_price

Submit price observations for products at specific stores to track global food prices across 27 countries. This tool enables real-time price data collection for comparison and aggregation.

Instructions

Submit a price observation for a product at a specific store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barcodeYesProduct barcode (8-14 digits)
country_codeYes2-letter country code
store_idYesStore ID (use list_stores to find valid IDs)
observed_priceYesPrice amount (positive number)
currencyYes3-letter currency code (e.g. "EUR", "TRY", "USD")
package_quantityYesPackage size amount
package_unitYesPackage unit
observed_atNoISO 8601 date (defaults to now)
product_variant_noteNoOptional note about the variant

Implementation Reference

  • The submit_price tool is registered and implemented directly in src/index.ts. It uses the api helper to send a POST request to the /api/prices endpoint.
      'submit_price',
      'Submit a price observation for a product at a specific store.',
      {
        barcode: z.string().describe('Product barcode (8-14 digits)'),
        country_code: z.string().length(2).describe('2-letter country code'),
        store_id: z.string().describe('Store ID (use list_stores to find valid IDs)'),
        observed_price: z.number().positive().describe('Price amount (positive number)'),
        currency: z.string().length(3).describe('3-letter currency code (e.g. "EUR", "TRY", "USD")'),
        package_quantity: z.number().positive().describe('Package size amount'),
        package_unit: z.enum(['g', 'kg', 'ml', 'l', 'pcs']).describe('Package unit'),
        observed_at: z.string().optional().describe('ISO 8601 date (defaults to now)'),
        product_variant_note: z.string().max(500).optional().describe('Optional note about the variant'),
      },
      async (input) => {
        try {
          const observation = await api('/api/prices', {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify(input),
          });
          return text(observation);
        } catch (e) {
          return errorResult(`Submit price failed: ${(e as Error).message}`);
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Submit' implies a write operation, the description does not clarify what happens upon submission (creates new record, updates existing, validation rules), side effects, idempotency, or error conditions.

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 is a single, efficient sentence (9 words) that front-loads the action. Every word earns its place with zero redundancy or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex write operation with 9 parameters, no annotations, and no output schema, the description is insufficient. It omits expected behavior (return value, success indication), prerequisites for valid submission, and the relationship between required parameters like barcode and observed_price.

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%, with all 9 parameters well-documented in the schema. The description adds no semantic value beyond the schema, which is acceptable given the high coverage baseline of 3.

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 clear verb ('Submit') and identifies the resource ('price observation') and context ('at a specific store'). It implicitly distinguishes from sibling read operations like get_prices, though it does not explicitly name alternatives.

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

Usage Guidelines2/5

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

The description states what the tool does but provides no guidance on when to use it versus alternatives, prerequisites (e.g., verifying the store exists), or when not to use it. The schema mentions using list_stores, but the description itself lacks usage guidance.

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