Skip to main content
Glama

product-barcode-api

by com.jojapi
OverviewDiscussionsAdmin

Product Search

get_api_external_search

Searches for products by barcode or name; returns a minimum of 1 and a maximum of 10 products. Billing per call: Credits: metered (~3.02 avg).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesIt allows the user to specify the name or barcode of the product they wish to search for. Using this parameter, the system searches for products based on name or barcode matches and returns the results.Çikolatalı Gofret
marketPricesNoThis setting controls whether price information for the requested products at stores is retrieved. If set to `true`, the product's store prices are also returned; if set to `false` or left unspecified, only the product's basic information is retrieved. If data is available, +1 credit is consumed for every 10 market price data points.false
historyPricesNoAdds historical price information for the requested product from available markets to the response. The `marketPrices` parameter must be set to `true`. If historical price information is available, 1 credit is consumed.false
preferredMarketsNoIt allows the user to specify the preferred markets for which they wish to view product prices. When this parameter is provided, price information is returned only for the listed markets within the `markets` field. If the parameter is not provided, price information for all markets is displayed. Users can specify multiple markets by separating them with commas (e.g., `preferredMarkets=A101,Migros`). If data is available, 1 credit is consumed for every 10 market-price data points.A101,Migros

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / marketPrices / description
      Previous value: -"It controls whether or not price information for the requested products at stores is retrieved. If set to `true`, the product's store prices are also returned; if set to `false` or left unspecified, only the product's basic information is retrieved. If data is available, +1 credit is spent for each market-price data point."New value: +"This setting controls whether price information for the requested products at stores is retrieved. If set to `true`, the product's store prices are also returned; if set to `false` or left unspecified, only the product's basic information is retrieved. If data is available, +1 credit is consumed for every 10 market price data points."
    • changedInput schema / properties / preferredMarkets / description
      Previous value: -"It allows the user to specify the preferred markets for which they wish to see product prices. If this parameter is provided, price information is returned in the `markets` field only for the markets listed. If the parameter is not provided, price information for all markets is displayed. If the user wishes to specify multiple markets, they can submit them separated by commas (e.g., `preferredMarkets=A101,Migros`). If data is available, +1 credit is consumed for each market-price data point."New value: +"It allows the user to specify the preferred markets for which they wish to view product prices. When this parameter is provided, price information is returned only for the listed markets within the `markets` field. If the parameter is not provided, price information for all markets is displayed. Users can specify multiple markets by separating them with commas (e.g., `preferredMarkets=A101,Migros`). If data is available, 1 credit is consumed for every 10 market-price data points."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two genuinely useful traits: the 1-10 result bound and the metered billing (~3.02 credits avg), which are not in the schema. However, it says nothing about authentication requirements, failure/empty-result behavior, or how the per-parameter credit costs interact with the base call cost.

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?

A single front-loaded sentence carrying purpose, result bounds, and billing with zero filler. Every clause earns its place.

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?

No output schema exists, but the description supplies the return cardinality (1-10) that the schema lacks, and the input schema is rich at 100% coverage. The main residual gap is the absence of annotations and any auth/error context, which leaves the safety and failure profile undescribed.

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%, so all four parameters including the credit costs for marketPrices/historyPrices/preferredMarkets are already fully documented in the schema. The description adds nothing about parameter semantics or the dependency (historyPrices requires marketPrices=true), so the baseline 3 applies.

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?

States a specific verb and resource ('Searches for products') plus the matching keys ('by barcode or name') and the result cardinality bound (1-10). This is clear on its own, but it never names or contrasts with the sibling getProducts, so an agent cannot tell the two apart without opening both schemas.

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?

Usage is only implied: searching by name or barcode suggests a lookup scenario, but there is no explicit when-to-use, no exclusions, and no pointer to alternatives such as getProducts or product_of_market. An agent must infer routing from the sibling list alone.

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

All product-barcode-api toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources