Skip to main content
Glama

Get Alphamega products by id or barcode

get_products
Read-only

Look up specific products by store ID (SKU) or EAN barcode to retrieve Greek titles, descriptions, ingredients, and see which IDs or barcodes were not found.

Instructions

Look up specific products by store id (SKU) and/or EAN barcode. Returns full details including Greek title, description and ingredients, plus the ids/barcodes that were not found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoProduct ids, e.g. ["487888"].
barcodesNoEAN/UPC barcodes, e.g. ["5290129000813"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, yet the description still adds real value: it says the response includes full details (Greek title, description, ingredients) and, importantly, that ids/barcodes which were not found are returned. That partial-failure behavior is exactly the kind of trait annotations do not convey.

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 sentences, no filler. The lookup keys come first and the return-value note second, which is the right order for an agent deciding whether to call it.

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?

For a two-optional-parameter read tool with no output schema, the description covers inputs, returned content, and not-found reporting. The one gap is that "and/or" does not specify whether supplying both ids and barcodes unions or intersects the results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds two things the schema does not: that "ids" are store ids/SKUs (the schema only says "Product ids") and that the two parameters may be used together via "and/or". The exact combination semantics when both are supplied remain unstated.

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 gives a specific verb and resource ("Look up specific products") and names the exact lookup keys: store id (SKU) and/or EAN barcode. That is enough to separate it from a free-text search, though the sibling search_products is never named, so a small amount of disambiguation is left to inference.

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?

"by store id (SKU) and/or EAN barcode" implicitly tells the agent this is for known-identifier lookups rather than browsing, but there is no explicit when-to-use or when-not-to-use statement and search_products is not contrasted. The guidance is implied rather than stated.

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