SendaMeal Storefront

get_product_details

Get product details (variants, options and images) by product ID(s).

Arguments: productIds - array of product IDs to get details for (from 'search_products'). [IMPORTANT] Request only the products the user needs. A server-configured limit applies (default 20); requests over the limit are rejected with an error (retry with fewer IDs). option_values - resolve a specific variant by option/value IDs. Only valid with a SINGLE productId, and applied on the B2C storefront catalog. B2B buyers instead receive every variant (each with its option/value IDs) and pick the desired one from the returned list. channelId - optional; scopes the B2B catalog. Defaults to the channel resolved from the request.

Returns:

products: array of products, each with:
- variants: each carrying entityId, SKU, and options (optionId, optionLabel, valueId, valueLabel).
- For B2B buyers, variants also include price, inventoryLevel, purchaseable, and bulkPricing.
Products not found are omitted from the array.

Flow:

Call 'search_products' to get product IDs.
Call this tool with the product IDs to get variants, options and images.
Call 'add_item_to_cart' with results of 'search_products' and 'get_product_details' (variant) tools.
- [IMPORTANT] If a product has variants you must specify which variant to add.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channelId`	No
`productIds`	Yes
`option_values`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`success`	Yes
`products`	Yes
`totalCount`	Yes

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description fully discloses key behaviors: server-configured limit (default 20), rejection over limit, B2B/B2C differences, and that products not found are omitted. This goes beyond the structured schema.

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 well-structured with clear sections (main purpose, arguments, returns, flow). Each sentence adds necessary detail, such as the limit warning and variant selection note, without redundancy.

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

Completeness5/5

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

The description covers the full context: flow, return structure, edge cases (limit, B2B/B2C, omitted products), and relationship to sibling tools. Given the tool's complexity, it is remarkably complete.

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

Parameters5/5

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

Schema coverage is 0%, but the description explains each parameter in depth: productIds (source, limit), option_values (single productId, B2C/B2B difference), channelId (B2B scoping, default). Fully compensates for the absent schema descriptions.

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?

The description clearly states 'Get product details (variants, options and images) by product ID(s)' with a specific verb and resource. It distinguishes itself from siblings by placing it in a flow: 'search_products' → 'get_product_details' → 'add_item_to_cart'.

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

Usage Guidelines5/5

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

Explicitly provides a flow: 'Call search_products to get product IDs. Call this tool with the product IDs...' and warns about variant selection. It also details when option_values is valid (single productId, B2C) versus B2B behavior, giving clear alternatives.

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

All SendaMeal Storefront tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: searching products, fetching details, adding/removing/updating cart items, and creating a checkout URL. There is no functional overlap between the six tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., search_products, add_item_to_cart, create_checkout_url). This makes the toolset predictable and easy to navigate.

Tool Count5/5

Six tools is well-scoped for a storefront server, covering the essential product discovery and cart management lifecycle without being bloated or too sparse.

Completeness3/5

The toolset covers product search, product details, cart additions/updates/removals, and checkout URL generation, but lacks a way to view the current cart contents. This is a notable gap since agents need to know what is already in the cart to manage it effectively.

Resources

Need Help?